| | 1 | == Table of Contents == |
| | 2 | |
| | 3 | |
| | 4 | 1. Introduction |
| | 5 | |
| | 6 | * 1.1. Design goals |
| | 7 | * 1.2. Architecture Summary |
| | 8 | * 1.3. Protocol Stack |
| | 9 | |
| | 10 | 2. Conventions used in this document |
| | 11 | |
| | 12 | 3. !MobilityFirst Network Protocol |
| | 13 | * 3.1. Design Principles |
| | 14 | * 3.2. Reliable Hop-by-Hop Block Transport |
| | 15 | * 3.3. Dynamic Name Resolution |
| | 16 | * 3.3.1. Early Binding |
| | 17 | * 3.3.2. Late Binding |
| | 18 | * 3.4. Hybrid Name-Address Routing |
| | 19 | * 3.4.1. Network name: GUID |
| | 20 | * 3.4.2. Network Address: Locator |
| | 21 | * 3.4.3. Multi-Homed Entities and Groups |
| | 22 | * 3.5. In-Network Delivery Services |
| | 23 | * 3.6. Service-Oriented Routing Header |
| | 24 | * 3.6.1. Service Header Extension |
| | 25 | |
| | 26 | 4. Name Certification Services |
| | 27 | * 4.1. Service API |
| | 28 | * 4.2. Protocol |
| | 29 | * 4.3. GUID Generation |
| | 30 | * 4.3.1. Identity-based GUID Generation |
| | 31 | * 4.3.2. User-Generated GUID |
| | 32 | * 4.4. Security Considerations |
| | 33 | |
| | 34 | 5. Global Name Resolution Service (GNRS) |
| | 35 | * 5.1. Service Interface |
| | 36 | * 5.1.1. Insert (and Update) GUID-to-Locator Mapping |
| | 37 | * 5.1.2. Query Locator(s) for a GUID |
| | 38 | * 5.2. GNRS Protocol |
| | 39 | * 5.2.1. Hierarchical Organization |
| | 40 | * 5.2.2. Security Considerations |
| | 41 | * 5.3. Scale and Performance Considerations |
| | 42 | * 5.4. Realization 1: Single-Hop In-Network Hashing |
| | 43 | * 5.5. Realization 2: Distributed Name Resolution Service – Arun’s Scheme |
| | 44 | |
| | 45 | 6. Generalized Edge-Aware Routing |
| | 46 | * 6.1. Network Organization: Networks, Sub-Networks, and Ad-Hoc Networks |
| | 47 | * 6.1.1. V-Nodes |
| | 48 | * 6.1.2. Limitations of Present Protocols and Goals for Future Internet |
| | 49 | * 6.2. Inter-Domain Routing Protocol |
| | 50 | * 6.2.1. Telescoped Dissemination of Path Information |
| | 51 | * 6.3. Intra-Domain (Edge) Routing: Generalized Storage Aware Routing (GSTAR) |
| | 52 | * 6.4. Scalable Multicast Using Heuristic Forwarding |
| | 53 | * 6.5. Ad-Hoc Networks |
| | 54 | * 6.6. Stability Considerations |
| | 55 | * 6.7. Security Considerations |
| | 56 | * 6.7.1. Secure Routing Exchanges |
| | 57 | |
| | 58 | 7. Network Management |
| | 59 | * 7.1. Design Principles |
| | 60 | * 7.2. Architecture |
| | 61 | * 7.3. Interfaces To Access Network State |
| | 62 | * 7.4. Roaming and Host/Client Management (AAA) |
| | 63 | * 7.5. Fault Tolerance Considerations |
| | 64 | * 7.6. Security Considerations |
| | 65 | |
| | 66 | 8. Compute Plane and Value Added Services |
| | 67 | * 8.1. Extensible Network Service Architecture |
| | 68 | * 8.2. Service API |
| | 69 | * 8.3. Security Considerations |
| | 70 | * 8.4. Sample Services |
| | 71 | |
| | 72 | 9. MF Use Case 1: Content a First Class Network Entity |
| | 73 | * 9.1. Content Naming, Publishing and Discovery |
| | 74 | * 9.2. Content Dissemination/Retrieval Protocol |
| | 75 | * 9.2.1. Security Considerations |
| | 76 | * 9.3. In-Network Caching |
| | 77 | * 9.4. Scalability and Performance Considerations |
| | 78 | |
| | 79 | 10. MF Use Case 2: M2M Application Support |
| | 80 | * 10.1. Naming Considerations |
| | 81 | * 10.2. End-point Resource Considerations and Function Offloading |
| | 82 | |
| | 83 | 11. MF Use Case 3: Support for Context Applications |
| | 84 | * 11.1. What constitutes a context? |
| | 85 | * 11.2. Representing Contexts in !MobilityFirst |
| | 86 | * 11.3. Component Architecture |
| | 87 | * 11.4. End-to-End Protocol |
| | 88 | |
| | 89 | 12. Discussion of Open Issues |
| | 90 | |
| | 91 | 13. Conclusions |
| | 92 | |
| | 93 | 14. References |
| | 94 | * 14.1. Normative References |
| | 95 | * 14.2. Informative References |
| | 96 | 15. Acknowledgments |
| | 97 | Appendix A. !MobilityFirst Packet Header Definitions |
| | 98 | * A.1. Service Header Extensions for Common Services |
| | 99 | * A.2. Hexadecimal SID Values for Proposed Services |
