I-D ACTION:draft-ietf-ospf-2547-dnbit-00.txt

Internet-Drafts@ietf.org Tue, 24 June 2003 11:26 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12092 for <ospf-archive@LISTS.IETF.ORG>; Tue, 24 Jun 2003 07:26:27 -0400 (EDT)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <17.00A2DBC6@cherry.ease.lsoft.com>; Tue, 24 Jun 2003 7:21:16 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 46450319 for OSPF@PEACH.EASE.LSOFT.COM; Tue, 24 Jun 2003 07:21:15 -0400
Received: from 132.151.1.176 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Tue, 24 Jun 2003 07:11:14 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11285; Tue, 24 Jun 2003 07:00:42 -0400 (EDT)
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Message-ID: <200306241100.HAA11285@ietf.org>
Date: Tue, 24 Jun 2003 07:00:42 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Comments: RFC822 error: <W> Incorrect or incomplete address field found and ignored.
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-ospf-2547-dnbit-00.txt
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Open Shortest Path First IGP Working Group of the IETF.

        Title           : Using an LSA Options Bit to Prevent Looping in
                          BGP/MPLS IP VPNs
        Author(s)       : E. Rosen et al.
        Filename        : draft-ietf-ospf-2547-dnbit-00.txt
        Pages           : 6
        Date            : 2003-6-23

[VPN] describes a method by which a Service Provider (SP) may provide
an 'IP VPN' service to its customers.  In VPNs of that sort, a
Customer Edge (CE) Router and a Provider Edge Router become routing
peers, and the customer routes are sent to the SP.  BGP is then used
to carry the customer routes across the SP's backbone to other PE
routers, and the routes are then sent to other CE routers.  Since CE
routers and PE routers are routing peers, it is customary to run a
routing protocol between them.  [VPN] allows a number of different
PE-CE protocols.  If OSPF is used as the PE-CE routing protocol, the
PE must execute additional procedures not specified in [VPN]; these
procedures are specified in [OSPF-VPN].  These additional procedures
translate customer OSPF routes from a CE router into BGP routes.  The
BGP routes are sent to the other PE routers, which translate them
back into OSPF routes, and then distribute them to CE routers.
During this translation, some of the information needed to prevent
loops may be lost.  The procedures specified in this document remedy
this situation by specifying that one of the OSPF options bits be
used to ensure that when a VPN route is sent from a PE to a CE, the
route will be ignored by any PE which receives it back from a CE.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ospf-2547-dnbit-00.txt

To remove yourself from the IETF Announcement list, send a message to
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
        "get draft-ietf-ospf-2547-dnbit-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-ietf-ospf-2547-dnbit-00.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-ospf-2547-dnbit-00.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-ospf-2547-dnbit-00.txt>