RFC 6788 on The Line-Identification Option

rfc-editor@rfc-editor.org Mon, 19 November 2012 20:36 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68F7E21F875F; Mon, 19 Nov 2012 12:36:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.926
X-Spam-Level:
X-Spam-Status: No, score=-101.926 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DjQaf4JABmnn; Mon, 19 Nov 2012 12:36:08 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id E11BF21F872A; Mon, 19 Nov 2012 12:36:07 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id AABEEB1E002; Mon, 19 Nov 2012 12:28:49 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6788 on The Line-Identification Option
From: rfc-editor@rfc-editor.org
Message-Id: <20121119202849.AABEEB1E002@rfc-editor.org>
Date: Mon, 19 Nov 2012 12:28:49 -0800
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2012 20:36:08 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6788

        Title:      The Line-Identification Option 
        Author:     S. Krishnan, A. Kavanagh,
                    B. Varga, S. Ooghe, E. Nordmark
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2012
        Mailbox:    suresh.krishnan@ericsson.com, 
                    alan.kavanagh@ericsson.com, 
                    balazs.a.varga@ericsson.com,
                    sven.ooghe@alcatel-lucent.com, 
                    nordmark@cisco.com
        Pages:      17
        Characters: 38410
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-6man-lineid-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6788.txt

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 in which multiple user ports are mapped to
the same virtual interface on the Edge Router.  [STANDARDS-TRACK]


This document is a product of the IPv6 Maintenance Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC