[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[RRG] mapping "issues" list from this morning
- To: RRG Mailing List <rrg@psg.com>
- Subject: [RRG] mapping "issues" list from this morning
- From: Scott Brim <swb@employees.org>
- Date: Tue, 11 Mar 2008 17:05:32 -0400
- User-agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
Attached is the list of criteria from this morning, modulo a little
editing. This is not complete. Please add *and* delete and clarify.
My own comments will follow.
Scott
Support for other network needs
-------------------------------
- Mobility.
- Impact on preferences for mobility approaches
- Does it meet mobility requirements
- Emergency services.
Delay and/or Drop of initial packets
------------------------------------
- Whether there will be any delay at all (might even get there
faster).
- Number of packets that might be delayed, dropped.
- Between sites and/or hosts.
- Trade off determinism of delay/drop versus agility & light weight.
Analyze based on how bad it would be.
- Effect on transport layer, session.
- Ultimately only end user experience is visible.
- Possibility of difference classes of service?
Push, Poll, Hybrids
-------------------
- Possibly proactive, dynamic adjustment of behavior.
- By src/dst (site)
- Responsiveness
- Other parameters?
Security considerations
-----------------------
- Interactions with drop/delay. (Eliot Lear -- needs clarification
please).
- Authorization: Don't take requestors down garden path. Don't give
them information they aren't authorized to actually use.
- Security of mapping system itself: updates authenticated .
- Authentication of map replies.
- Interactions between security of mapping system and security of core
routing.
Granularity
-----------
- What level of specificity?
- Ability to operate at multiple levels of granularity simultaneously.
Churn
-----
- How system responds with rate of intentional changes.
Mapping points
--------------
- Flexibility in mapping points: end system, domain border, in
between.
- Placement of mapping points: those that own the mappings, those that
use them, or in a third party
- Who is authoritative for the mapping. Owner, holder, user.
Interaction between rate, state, and delay
--------------------------------------
- Interaction between rate, state, and delay.
Deployability (Incremental)
---------------------------
- Interworking with existing deployments.
- How soon are benefits seen?
- Who gains. Is it the one doing the deployment?
- Does a deployment require more than one party, coordinated?
- Easing v4=>v6 is not an issue.
Flexibility
-----------
- Possibility for hierarchy
- Ability to express preferences (policy)
Failure modes
-------------
- How does mapping system adapt to unintentional changes in reachability (if at
all).
- Dependence on something not on the data path (-> uncontrolled weaknesses).
- Resilience of mapping system.