The Line Identification Destination Option
draft-ietf-6man-lineid-04

The information below is for an old version of the document
Document Type Active Internet-Draft (6man WG)
Last updated 2012-05-02 (latest revision 2012-03-09)
Stream IETF
Intended RFC status Experimental
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state AD Evaluation::Revised I-D Needed
Telechat date
Responsible AD Brian Haberman
IESG note Bob Hinden (bob.hinden@gmail.com) is the Document Shepherd.
Send notices to 6man-chairs@tools.ietf.org, draft-ietf-6man-lineid@tools.ietf.org
6man Working Group                                           S. Krishnan
Internet-Draft                                               A. Kavanagh
Intended status: Experimental                                   B. Varga
Expires: September 10, 2012                                     Ericsson
                                                                S. Ooghe
                                                          Alcatel-Lucent
                                                             E. Nordmark
                                                                   Cisco
                                                           March 9, 2012

               The Line Identification Destination Option
                       draft-ietf-6man-lineid-04

Abstract

   In Ethernet based aggregation networks, several subscriber premises
   may be logically connected to the same interface of an edge router.
   This document proposes a method for the edge router to identify the
   subscriber premises using the contents of the received Router
   Solicitation messages.  The applicability is limited to broadband
   network deployment scenarios where multiple user ports are mapped to
   the same virtual interface on the Edge Router.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 10, 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

Krishnan, et al.       Expires September 10, 2012               [Page 1]
Internet-Draft         Line ID Destination Option             March 2012

   (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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  4
     1.2.  Conventions used in this document  . . . . . . . . . . . .  5
   2.  Applicability Statement  . . . . . . . . . . . . . . . . . . .  6
   3.  Issues with identifying the subscriber in an N:1 VLAN model  .  6
   4.  Basic operation  . . . . . . . . . . . . . . . . . . . . . . .  7
   5.  Access Node Behavior . . . . . . . . . . . . . . . . . . . . .  7
     5.1.  On receiving a Router Solicitation from the end-device . .  7
     5.2.  On receiving a Router Advertisement from the Edge
           Router . . . . . . . . . . . . . . . . . . . . . . . . . .  8
       5.2.1.  Identifying tunneled Router Advertisements . . . . . .  8
     5.3.  On detecting a subscriber circuit coming up  . . . . . . .  8
     5.4.  On detecting Edge Router failure . . . . . . . . . . . . .  8
     5.5.  RS Retransmission algorithm  . . . . . . . . . . . . . . .  9
   6.  Edge Router Behavior . . . . . . . . . . . . . . . . . . . . .  9
     6.1.  On receiving a Tunneled Router Solicitation from the
           Access Node  . . . . . . . . . . . . . . . . . . . . . . .  9
     6.2.  On sending a Router Advertisement towards the
           end-device . . . . . . . . . . . . . . . . . . . . . . . .  9
     6.3.  Sending periodic unsolicited Router Advertisements
           towards the end-device . . . . . . . . . . . . . . . . . . 10
   7.  Line Identification Destination Option (LIO) . . . . . . . . . 10
     7.1.  Encoding of Line ID  . . . . . . . . . . . . . . . . . . . 11
   8.  Garbage collection of unused prefixes  . . . . . . . . . . . . 12
   9.  Interactions with Secure Neighbor Discovery  . . . . . . . . . 12
   10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
   11. Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   12. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 13
   13. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Show full document text