Optional Advanced Deployment Scenarios for ILNP
draft-irtf-rrg-ilnp-adv-05
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2012-05-30
|
|
Stream |
|
IRTF
|
|
Intended RFC status |
|
Experimental
|
|
Formats |
|
plain text
pdf
html
bibtex
|
Stream |
IRTF state
|
|
(None)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Document shepherd |
|
None
|
IESG |
IESG state |
|
Approved-announcement sent
|
|
Telechat date |
|
|
|
Responsible AD |
|
Stephen Farrell
|
|
IESG note |
|
Tony Li (tony.li@tony.li) is the document shepherd.
|
|
Send notices to |
|
rja.lists@gmail.com, saleem@cs.st-andrews.ac.uk, draft-irtf-rrg-ilnp-adv@tools.ietf.org, tony.li@tony.li
|
Internet Draft RJ Atkinson
draft-irtf-rrg-ilnp-adv-05.txt Consultant
Expires: 29 Nov 2012 SN Bhatti
Category: Experimental U. St Andrews
29 May 2012
Optional Advanced Deployment Scenarios for ILNP
draft-irtf-rrg-ilnp-adv-05.txt
Status of this Memo
Distribution of this memo is unlimited.
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. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e
of the Trust Legal Provisions and are provided without warranty
as described in the Simplified BSD License.
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
This document may contain material from IETF Documents or
IETF Contributions published or made publicly available
before November 10, 2008. The person(s) controlling the copyright
in some of this material may not have granted the IETF Trust the
right to allow modifications of such material outside the IETF
Standards Process. Without obtaining an adequate license from the
person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process,
and derivative works of it may not be created outside the IETF
Standards Process, except to format it for publication as an RFC
or to translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
Atkinson & Bhatti Expires in 6 months [Page 1]
Internet Draft ILNP ADV 29 MAY 2012
documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in
progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
This document is not on the IETF standards-track and does not
specify any level of standard. This document merely provides
information for the Internet community.
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.
Table of Contents
1. Introduction......................................?
2. Localised Numbering...............................?
3. An Alternative For Site Multi-Homing..............?
4. An Alternative For Site (Network) Mobility........?
5. Traffic Engineering Options.......................?
6. ILNP in Datacentres ..............................?
7. Location Privacy..................................?
8. Identity Privacy..................................?
9. Security Considerations...........................?
10. IANA Considerations...............................?
11. References........................................?
1. INTRODUCTION
ILNP is, in essence, an end-to-end architecture: the
functions required for ILNP are implemented in, and controlled
by, only those end-systems that wish to use ILNP, as described
in [ILNP-ARCH]. Other nodes, such as Site Border Routers (SBRs)
Atkinson & Bhatti Expires in 6 months [Page 2]
Internet Draft ILNP ADV 29 MAY 2012
need only support IP to allow operation of ILNP, e.g. an SBR
should support IPv6 in order to enable end-systems to operate
ILNPv6 within the site network for which an SBR provides a
service [ILNP-ENG].
However, some features of ILNP could be optimised, from an
engineering perspective, by the use of an intermediate system (a
router, security gateway or "middlebox") that modifies (rewrites)
Show full document text