Table of Contents
- Introduction
- 1.1. Design goals
- 1.2. Architecture Summary
- 1.3. Protocol Stack
- Conventions used in this document
- MobilityFirst Network Protocol (Kiran)
- 3.1. Design Principles
- 3.2. Reliable Hop-by-Hop Block Transport
- 3.3. Dynamic Name Resolution
- 3.3.1. Early Binding
- 3.3.2. Late Binding
- 3.4. Hybrid Name-Address Routing
- 3.4.1. Network name: GUID
- 3.4.2. Network Address: Locator
- 3.4.3. Multi-Homed Entities and Groups
- 3.5. In-Network Delivery Services
- 3.6. Service-Oriented Routing Header
- 3.6.1. Service Header Extension
- Name Certification Services (Jun, Ray?)
- 4.1. Service API
- 4.2. Protocol
- 4.3. GUID Generation
- 4.3.1. Identity-based GUID Generation
- 4.3.2. User-Generated GUID
- 4.4. Security Considerations (Wade, Janne?)
- Global Name Resolution Service (GNRS) (Akash, Tam)
- 5.1. Service Interface
- 5.1.1. Insert (and Update) GUID-to-Locator Mapping
- 5.1.2. Query Locator(s) for a GUID
- 5.2. GNRS Protocol
- 5.2.1. Hierarchical Organization
- 5.2.2. Security Considerations (Wade, Janne?)
- 5.3. Scale and Performance Considerations
- 5.4. Realization 1: Single-Hop In-Network Hashing
- 5.5. Realization 2: Distributed Name Resolution Service – Arun’s Scheme (Arun?)
- 5.1. Service Interface
- Generalized Edge-Aware Routing (Tam, Kiran, Ray)
- 6.1. Network Organization: Networks, Sub-Networks, and Ad-Hoc Networks
- 6.1.1. V-Nodes
- 6.1.2. Limitations of Present Protocols and Goals for Future Internet
- 6.2. Inter-Domain Routing Protocol
- 6.2.1. Telescoped Dissemination of Path Information
- 6.2.2. Morley's Scheme (Morley?)
- 6.3. Intra-Domain (Edge) Routing: Generalized Storage Aware Routing (GSTAR)
- 6.4. Scalable Multicast Using Heuristic Forwarding
- 6.5. Ad-Hoc Networks
- 6.6. Stability Considerations
- 6.7. Security Considerations (Wade, Janne?)
- 6.7.1. Secure Routing Exchanges
- 6.1. Network Organization: Networks, Sub-Networks, and Ad-Hoc Networks
- Network Management (Kiran, Suman, Jim?)
- 7.1. Design Principles
- 7.2. Architecture
- 7.3. Interfaces To Access Network State
- 7.4. Roaming and Host (or Client) Management (AAA)
- 7.5. Fault Tolerance Considerations
- 7.6. Security Considerations (Wade, Janne?)
- Compute Plane and Value Added Services (Yang, Xiaowei, Kiran)
- 8.1. Extensible Network Service Architecture
- 8.2. Service API
- 8.3. Security Considerations
- 8.4. Sample Services
- MF Use Case 1: Content a First Class Network Entity (Kiran, Feixiong, Yanyong)
- 9.1. Content Naming, Publishing and Discovery
- 9.2. Content Retrieval Protocol
- 9.2.1. Security Considerations (Wade, Janne?)
- 9.3. In-Network Caching
- 9.4. Scalability and Performance Considerations
- MF Use Case 2: M2M and Sensor Application Support (Jun Li)
- 10.1. Naming Considerations
- 10.2. End-point Resource Considerations and Function Offloading
- MF Use Case 3: Support for Context Applications (John, Jun Li, Rich Martin)
- 11.1. What constitutes a context?
- 11.2. Representing Contexts in MobilityFirst
- 11.3. Component Architecture
- 11.4. End-to-End Protocol
- Discussion of Open Issues
- Conclusions
- References
- 14.1. Normative References
- 14.2. Informative References
- Acknowledgments
Appendix A. MobilityFirst Packet Header Definitions
- A.1. Service Header Extensions for Common Services
- A.2. Hexadecimal SID Values for Proposed Services
Last modified
12 years ago
Last modified on Apr 3, 2012, 6:50:42 PM
Note:
See TracWiki
for help on using the wiki.