Status of Multiple Next-Hops Drafts

Hello,

After following the discussion about a multiple next-hop extension to
BGP in August/September last year (draft-bhatia-bgp-multiple-next-hops
<--> draft-walton-bgp-add-paths), I haven't seen any new on mailing list
for a long time.

Are there any activities on these drafts at the moment or new versions
planed to publish in near future?

Especially addressed to the guys from Cisco:
How about an implementation of the add-paths draft in IOS, are there any
plans?

Regards.
Dan Bamberg

_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www1.ietf.org/mailman/listinfo/idr

I-D ACTION:draft-ietf-idr-rfc3065bis-06.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title		: Autonomous System Confederations for BGP
	Author(s)	: P. Traina, et al.
	Filename	: draft-ietf-idr-rfc3065bis-06.txt
	Pages		: 17
	Date		: 2007-2-2
	
The Border Gateway Protocol (BGP) is an inter-autonomous system
   routing protocol designed for Transmission Control Protocol/Internet
   Protocol (TCP/IP) networks.  BGP requires that all BGP speakers
   within a single autonomous system (AS) must be fully meshed.  This
   represents a serious scaling problem that has been well documented in
   a number of proposals.

   This document describes an extension to BGP which may be used to
   create a confederation of autonomous systems that is represented as a
   single autonomous system to BGP peers external to the confederation,
   thereby removing the "full mesh" requirement.  The intention of this
   extension is to aid in policy administration and reduce the
   management complexity of maintaining a large autonomous system.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-rfc3065bis-06.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 

Re: I-D ACTION:draft-ietf-idr-rfc3065bis-06.txt

Folks,
This update is meant to address comments from IDR and GEN-ART
review feedback and all outstanding issues should be accommodated.

A diff from -05 is available here:

http://tools.ietf.org/wg/idr/draft-ietf-idr-rfc3065bis/draft-ietf-idr- 
rfc3065bis-06-from-05.diff.html

Thanks to the GEN-ART team for their usual thorough review,
and to the folks here for additional feedback.

-danny

On Feb 2, 2007, at 1:50 PM, Internet-Drafts <at> ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Inter-Domain Routing Working Group  
> of the IETF.
>
> 	Title		: Autonomous System Confederations for BGP
> 	Author(s)	: P. Traina, et al.
> 	Filename	: draft-ietf-idr-rfc3065bis-06.txt
> 	Pages		: 17
> 	Date		: 2007-2-2
> 	
> The Border Gateway Protocol (BGP) is an inter-autonomous system
>    routing protocol designed for Transmission Control Protocol/ 

I-D ACTION:draft-ietf-idr-as4bytes-13.txt

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title		: BGP Support for Four-octet AS Number Space
	Author(s)	: Q. Vohra, E. Chen
	Filename	: draft-ietf-idr-as4bytes-13.txt
	Pages		: 10
	Date		: 2007-2-7
	
Currently the Autonomous System number is encoded as a two-octet
   entity in BGP. This document describes extensions to BGP to carry the
   Autonomous System number as a four-octet entity.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-idr-as4bytes-13.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

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-idr-as4bytes-13.txt".

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

[Fwd: I-D ACTION:draft-ietf-idr-as4bytes-13.txt]

Hi, folks:

The revised version addresses several comments from the IESG review, 
including:

      o IANA Considerations
      o Security Considerations
      o Attribute Naming

Please note these changes to the attribute names (the type codes are 
unchanged):

     NEW_AS_PATH             --->   AS4_PATH
     NEW_AGGREGATOR   --->   AS4_AGGREGATOR

Thanks.   -- Enke

-------- Original Message --------
Subject: 	I-D ACTION:draft-ietf-idr-as4bytes-13.txt
Date: 	Wed, 07 Feb 2007 15:50:02 -0500
From: 	Internet-Drafts <at> ietf.org
Reply-To: 	internet-drafts <at> ietf.org
To: 	i-d-announce <at> ietf.org
CC: 	idr <at> ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Inter-Domain Routing Working Group of the IETF.

	Title		: BGP Support for Four-octet AS Number Space

Re: [Fwd: I-D ACTION:draft-ietf-idr-as4bytes-13.txt]

Enke Chen <enkechen <at> cisco.com> wrote:
> 
> Please note these changes to the attribute names (the type codes are 
> unchanged):
> 
>     NEW_AS_PATH             --->   AS4_PATH
>     NEW_AGGREGATOR   --->   AS4_AGGREGATOR

   I attach an abbreviated diff with context for changes other than those.
Note in Section 4.1 "MAY advertise" becomes "SHOULD advertise", and in
Section 6 "SHOULD NOT use AS_TRANS" becomes "MUST NOT use AS_TRANS".

   Section 7 now includes actual assigned values, and explicitly disclaims
any intent to modify allocation policies and procedures.

   Section 8 adds a Security Consideration, which deserves to be read
carefully.

-------------------------------- cut here --------------------------------
3. Protocol Extensions
     attribute has the same semantics as the AGGREGATOR attribute, except
<    that it carries 4-octet AS numbers.
---
     attribute has the same semantics as the AGGREGATOR attribute, except
>    that it carries a 4-octet AS number.
****
     Currently assigned 2-octet Autonomous System numbers are converted
<    into 4-octet Autonomous System numbers by setting the high-order 2
     octets of the 4-octet field to zero. Such a 4-octet AS number is said
---

RFC 4798 on Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)

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

        
        RFC 4798

        Title:      Connecting IPv6 Islands over IPv4 
                    MPLS Using IPv6 Provider Edge Routers 
                    (6PE) 
        Author:     J. De Clercq, D. Ooms,
                    S. Prevost, F. Le Faucheur
        Status:     Standards Track
        Date:       February 2007
        Mailbox:    jeremy.de_clercq <at> alcatel-lucent.be, 
                    dirk <at> onesparrow.com, 
                    stuart.prevost <at> bt.com,  flefauch <at> cisco.com
        Pages:      14
        Characters: 31381
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ooms-v6ops-bgp-tunnel-07.txt

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

This document explains how to interconnect IPv6 islands over a
Multiprotocol Label Switching (MPLS)-enabled IPv4 cloud.  This
approach relies on IPv6 Provider Edge routers (6PE), which are Dual
Stack in order to connect to IPv6 islands and to the MPLS core, which is 
only required to run IPv4 MPLS.  The 6PE routers exchange the IPv6
reachability information transparently over the core using the

Re: [Fwd: I-D ACTION:draft-ietf-idr-as4bytes-13.txt]

On Wed, Feb 07, 2007 at 07:28:02PM -0500, John Leslie wrote:
> Enke Chen <enkechen <at> cisco.com> wrote:
> > 
> > Please note these changes to the attribute names (the type codes are 
> > unchanged):
> > 
> >     NEW_AS_PATH             --->   AS4_PATH
> >     NEW_AGGREGATOR   --->   AS4_AGGREGATOR

Perhaps a stupid question, but why not go for "AS4 speaker" and "AS2
speaker" too instread of "NEW/OLD speaker"?

cheers,
--

-- 
Erik Romijn                 RIPE NCC jr. software engineer
http://www.ripe.net/        Information Services dept.

_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www1.ietf.org/mailman/listinfo/idr

Re: [Fwd: I-D ACTION:draft-ietf-idr-as4bytes-13.txt]

Hi, Erik:

Erik Romijn wrote:
> On Wed, Feb 07, 2007 at 07:28:02PM -0500, John Leslie wrote:
>   
>> Enke Chen <enkechen <at> cisco.com> wrote:
>>     
>>> Please note these changes to the attribute names (the type codes are 
>>> unchanged):
>>>
>>>     NEW_AS_PATH             --->   AS4_PATH
>>>     NEW_AGGREGATOR   --->   AS4_AGGREGATOR
>>>       
>
> Perhaps a stupid question, but why not go for "AS4 speaker" and "AS2
> speaker" too instread of "NEW/OLD speaker"?
>
>   

Because the terminologies "NEW/OLD speaker" do not refer to protocol 
code points . They are used in the document only for the sake of 
presentation, and they seem to be a good fit for the intended purpose.

-- Enke

_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www1.ietf.org/mailman/listinfo/idr

about bgp label routes

_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www1.ietf.org/mailman/listinfo/idr