Optional Advanced Deployment Scenarios for the Identifier-Locator Network Protocol (ILNP)
RFC 6748
| Document | Type |
RFC - Experimental
(November 2012; No errata)
Was draft-irtf-rrg-ilnp-adv (rrg RG)
|
|
|---|---|---|---|
| Last updated | 2015-10-14 | ||
| Stream | IRTF | ||
| Formats | plain text pdf html bibtex | ||
| Stream | IRTF state | (None) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | RFC 6748 (Experimental) | |
| Telechat date | |||
| Responsible AD | Stephen Farrell | ||
| IESG note | Tony Li (tony.li@tony.li) is the document shepherd. | ||
| Send notices to | tony.li@tony.li | ||
Internet Research Task Force (IRTF) RJ Atkinson
Request for Comments: 6748 Consultant
Category: Experimental SN Bhatti
ISSN: 2070-1721 U. St Andrews
November 2012
Optional Advanced Deployment Scenarios for the
Identifier-Locator Network Protocol (ILNP)
Abstract
This document provides an Architectural description and the Concept
of Operations of some optional advanced deployment scenarios for the
Identifier-Locator Network Protocol (ILNP), which is an evolutionary
enhancement to IP. None of the functions described here is required
for the use or deployment of ILNP. Instead, it offers descriptions
of engineering and deployment options that might provide either
enhanced capability or convenience in administration or management of
ILNP-based systems.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for examination, experimental implementation, and
evaluation.
This document defines an Experimental Protocol for the Internet
community. This document is a product of the Internet Research Task
Force (IRTF). The IRTF publishes the results of Internet-related
research and development activities. These results might not be
suitable for deployment. This RFC represents the individual
opinion(s) of one or more members of the Routing Research Group of
the Internet Research Task Force (IRTF). Documents approved for
publication by the IRSG are not a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6748.
Atkinson & Bhatti Experimental [Page 1]
RFC 6748 ILNP ADV November 2012
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
This document may not be modified, and derivative works of it may not
be created, except to format it for publication as an RFC or to
translate it into languages other than English.
Atkinson & Bhatti Experimental [Page 2]
RFC 6748 ILNP ADV November 2012
Table of Contents
1. Introduction ....................................................4
1.1. Document Roadmap ...........................................5
1.2. Terminology ................................................6
2. Localised Numbering .............................................6
2.1. Localised Locators .........................................7
2.2. Mixed Local/Global Numbering ...............................9
2.3. Dealing with Internal Subnets with Locator Rewriting .......9
2.4. Localised Name Resolution with DNS ........................11
2.5. Use of mDNS ...............................................13
2.6. Site Network Name in DNS ..................................13
2.7. Site Interior Topology Obfuscation ........................14
2.8. Other SBR Considerations ..................................14
3. An Alternative for Site Multihoming ............................16
3.1. Site Multihoming (S-MH) Connectivity Using an SBR .........16
3.2. Dealing with Link/Connectivity Changes ....................17
3.3. SBR Updates to DNS ........................................18
3.4. DNS TTL Values for L32 and L64 Records ....................18
3.5. Multiple SBRs .............................................19
4. An Alternative for Site (Network) Mobility .....................20
4.1. Site (Network) Mobility ...................................20
4.2. SBR Updates to DNS ........................................22
4.3. DNS TTL Values for L32 and L64 Records ....................22
5. Traffic Engineering Options ....................................22
5.1. Load Balancing ............................................23
5.2. Control of Egress Traffic Paths ...........................24
6. ILNP in Datacentres ............................................26
Show full document text