internet-drafts | 28 Aug 22:07 2015
Picon

I-D Action: draft-ietf-rtgwg-bgp-routing-large-dc-07.txt


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

        Title           : Use of BGP for routing in large-scale data centers
        Authors         : Petr Lapukhov
                          Ariff Premji
                          Jon Mitchell
	Filename        : draft-ietf-rtgwg-bgp-routing-large-dc-07.txt
	Pages           : 34
	Date            : 2015-08-28

Abstract:
   Some network operators build and operate data centers that support
   over one hundred thousand servers.  In this document, such data
   centers are referred to as "large-scale" to differentiate them from
   smaller infrastructures.  Environments of this scale have a unique
   set of network requirements with an emphasis on operational
   simplicity and network stability.  This document summarizes
   operational experience in designing and operating large-scale data
   centers using BGP as the only routing protocol.  The intent is to
   report on a proven and stable routing design that could be leveraged
   by others in the industry.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-bgp-routing-large-dc/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-rtgwg-bgp-routing-large-dc-07

(Continue reading)

Chris Bowers | 24 Aug 20:32 2015
Picon

Poll for WG adoption of draft-lamparter-rtgwg-dst-src-routing-01

RTGWG,
 
This email starts a two-week poll on adopting draft-lamparter-rtgwg-dst-src-routing-01 as a working group document.
 
“Destination/Source Routing”
 
As was discussed in Prague, this draft is needed to support work in homenet.  It  is outside of the scope of homenet’s charter, but within the scope of RTGWG’s charter.
 
Please send comments to the list and state your support or opposition to RTGWG adoption of this draft. 
 
This poll runs through the end of Monday, September 7th.
 
If you are listed as a document author or contributor, please respond to this email stating whether or not you are aware of any relevant IPR.  The response needs to be sent to the RTGWG mailing list. The document will not advance to the next stage until a response has been received from each author and each individual that has contributed to the document.
 
Thanks,
Chris and Jeff
 
_______________________________________________
rtgwg mailing list
rtgwg <at> ietf.org
https://www.ietf.org/mailman/listinfo/rtgwg
Acee Lindem (acee | 21 Aug 23:51 2015
Picon

Quality Assurance Review of "Destination/Source Routing" - draft-lamparter-rtgwg-dst-src-routing-01

Hello David,

I have been selected as the Routing Directorate reviewer for this draft.
The Routing Directorate seeks to review all routing or routing-related
drafts as they pass through WG adoption, IETF last call, and IESG review,
and
sometimes on special request. The purpose of the review is to provide
assistance to the Routing ADs. For more information about the Routing
Directorate, please see
​http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir


Although these comments are primarily for the use of the Routing ADs, it
would be helpful if you could consider them along with any other IETF
Last Call comments that you receive, and strive to resolve them through
discussion or by updating the draft.


Since this is an initial QA review, I intend to focus on the main area
that require discussion in the WG.

Document: draft-lamparter-rtgwg-dst-src-routing-01
Reviewer: Acee Lindem
Review Date: 21 Aug 2015
Intended Status: Standards Track

Summary:

I believe the document is ready for Working Group adoption and further
discussion. 
There are a number of issues that needed to be resolved as part of the
normal
IETF process.

Issues for Resolution:

  Section 3.1: Ultimately we need to choose a variant for recursive route
      resolution. I believe we should choose one that simpler than variant
4.
      The reason being that BCP 38 is normally not a factor for use cases
where
      complex recursive resolution is required. However, this is a topic
for 
      WG discussion.

  Section 3.2: Again, I believe one option needs to be selected for uRPF
               filtering. I believe it should be pointed out that both the
source
               and destination are reversed in the uRPF lookup.

  Section 3.3: I don’t see why multicast is not applicable since there are
(S,G) 
               multicast routes (where the source is always /128).

  Section 4: Rather than expressing the constraints in terms of
forwarding, they
             should be expressed in terms of route installation and more
onus
             should be placed on the routing protocol.

Nits: I have some suggested editorial changes to the draft that I will
unicast 
to David. 

Thanks,
Acee 

  
               

  

_______________________________________________
rtgwg mailing list
rtgwg <at> ietf.org
https://www.ietf.org/mailman/listinfo/rtgwg
Jon Mitchell | 20 Aug 02:38 2015
Picon

Fw: New Version Notification for draft-ietf-rtgwg-bgp-routing-large-dc-06.txt


WG - 

This covers the comments received by Anoop in last call.

Thanks,

Jon

----- Forwarded message from internet-drafts <at> ietf.org -----

Date: Wed, 19 Aug 2015 17:36:16 -0700
From: internet-drafts <at> ietf.org
To: Jon Mitchell <jrmitche <at> puck.nether.net>, Ariff Premji <ariff <at> arista.com>, Petr Lapukhov
<petr <at> fb.com>, Ariff Premji
	<ariff <at> arista.com>, Petr Lapukhov <petr <at> fb.com>, Jon Mitchell <jrmitche <at> puck.nether.net>
Subject: New Version Notification for draft-ietf-rtgwg-bgp-routing-large-dc-06.txt

A new version of I-D, draft-ietf-rtgwg-bgp-routing-large-dc-06.txt
has been successfully submitted by Jon Mitchell and posted to the
IETF repository.

Name:		draft-ietf-rtgwg-bgp-routing-large-dc
Revision:	06
Title:		Use of BGP for routing in large-scale data centers
Document date:	2015-08-19
Group:		rtgwg
Pages:		34
URL:            https://www.ietf.org/internet-drafts/draft-ietf-rtgwg-bgp-routing-large-dc-06.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-rtgwg-bgp-routing-large-dc/
Htmlized:       https://tools.ietf.org/html/draft-ietf-rtgwg-bgp-routing-large-dc-06
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-bgp-routing-large-dc-06

Abstract:
   Some network operators build and operate data centers that support
   over one hundred thousand servers.  In this document, such data
   centers are referred to as "large-scale" to differentiate them from
   smaller infrastructures.  Environments of this scale have a unique
   set of network requirements with an emphasis on operational
   simplicity and network stability.  This document summarizes
   operational experience in designing and operating large-scale data
   centers using BGP as the only routing protocol.  The intent is to
   report on a proven and stable routing design that could be leveraged
   by others in the industry.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

----- End forwarded message -----
Santosh P K | 19 Aug 14:59 2015
Picon

FW: New Version Notification for draft-spallagatti-rtgwg-bandwidth-based-metric-01.txt

Hello All,
      A new version of IGP BBM draft has been submitted. Changes are related to review comments received from
IETF-92 and IETF-93. Please do review this new version of draft and get back to us with more comments. 

Thanks
Santosh P K 

> -----Original Message-----
> From: internet-drafts <at> ietf.org [mailto:internet-drafts <at> ietf.org]
> Sent: Wednesday, August 19, 2015 6:23 PM
> To: Santosh P K <santoshpk <at> juniper.net>; Pushpasis Sarkar
> <psarkar <at> juniper.net>; Stephane Litkowski
> <stephane.litkowski <at> orange.com>; Santosh P K <santoshpk <at> juniper.net>;
> Hannes Gredler <hannes <at> juniper.net>; Pushpasis Sarkar
> <psarkar <at> juniper.net>; Hannes Gredler <hannes <at> juniper.net>; Stephane
> Litkowski <stephane.litkowski <at> orange.com>
> Subject: New Version Notification for draft-spallagatti-rtgwg-bandwidth-
> based-metric-01.txt
> 
> 
> A new version of I-D, draft-spallagatti-rtgwg-bandwidth-based-metric-01.txt
> has been successfully submitted by Santosh Pallagatti and posted to the IETF
> repository.
> 
> Name:		draft-spallagatti-rtgwg-bandwidth-based-metric
> Revision:	01
> Title:		IGP bandwidth based metric.
> Document date:	2015-08-19
> Group:		Individual Submission
> Pages:		15
> URL:            https://www.ietf.org/internet-drafts/draft-spallagatti-rtgwg-
> bandwidth-based-metric-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-spallagatti-rtgwg-
> bandwidth-based-metric/
> Htmlized:       https://tools.ietf.org/html/draft-spallagatti-rtgwg-bandwidth-
> based-metric-01
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-spallagatti-rtgwg-
> bandwidth-based-metric-01
> 
> Abstract:
>    This document describes a method to group multiple interfaces and
>    assign metric to that group based on the cumulative bandwidth of all
>    the interfaces in that group.  Each link in a group takes same group
>    metric irrespective of its own bandwidth.
> 
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
Jeff Tantsura | 18 Aug 12:24 2015
Picon

IETF93 RTGWG minutes

Hi RTGWG,

Minutes are at: 
https://www.ietf.org/proceedings/93/minutes/minutes-93-rtgwg
Please provide your comments/suggestions.

Thanks!
Jeff & Chris
Pierre Francois (pifranco | 17 Aug 15:40 2015
Picon

FW: New Version Notification for draft-francois-rtgwg-segment-routing-ti-lfa-00.txt


Hello everyone, 

Here comes the re-submission of the ti-lfa draft to rtgwg, as discussed
during last IETF. 

Regards,

Pierre.

On 17/08/15 15:39, "internet-drafts <at> ietf.org" <internet-drafts <at> ietf.org>
wrote:

>
>A new version of I-D, draft-francois-rtgwg-segment-routing-ti-lfa-00.txt
>has been successfully submitted by Pierre Francois and posted to the
>IETF repository.
>
>Name:		draft-francois-rtgwg-segment-routing-ti-lfa
>Revision:	00
>Title:		Topology Independent Fast Reroute using Segment Routing
>Document date:	2015-08-17
>Group:		Individual Submission
>Pages:		10
>URL:            
>https://www.ietf.org/internet-drafts/draft-francois-rtgwg-segment-routing-
>ti-lfa-00.txt
>Status:         
>https://datatracker.ietf.org/doc/draft-francois-rtgwg-segment-routing-ti-l
>fa/
>Htmlized:       
>https://tools.ietf.org/html/draft-francois-rtgwg-segment-routing-ti-lfa-00
>
>
>Abstract:
>   This document presents Topology Independent Loop-free Alternate Fast
>   Re-route (TI-LFA), aimed at providing link and node protection of
>   node and adjacency segments within the Segment Routing (SR)
>   framework.  This Fast Re-route (FRR) behavior builds on proven IP-FRR
>   concepts being LFAs, remote LFAs (RLFA), and remote LFAs with
>   directed forwarding (DLFA).  It extends these concepts to provide
>   guaranteed coverage in any IGP network.  We accommodate the FRR
>   discovery and selection approaches in order to establish protection
>   over post-convergence paths from the point of local repair,
>   dramatically reducing the operational need to control the tie-breaks
>   among various FRR options.
>
>                  
>        
>
>
>Please note that it may take a couple of minutes from the time of
>submission
>until the htmlized version and diff are available at tools.ietf.org.
>
>The IETF Secretariat
>
Jeff Tantsura | 3 Aug 05:31 2015
Picon

RTGWG LC for draft-ietf-rtgwg-bgp-routing-large-dc

Hi RTGWG,

This email is to start 2 weeks RTGWG LC for
draft-ietf-rtgwg-bgp-routing-large-dc-05
Authors have addressed all the comments.

Please indicate support or no-support as well as your comments by August
18, 2015.

If you are listed as a document author or contributor please respond to
this email stating of whether or not you are aware of any relevant IPR.
The response needs to be sent to the RTGWG mailing list. The document will
not advance to the next stage until a response has been received from each
author and each individual that has contributed to the document.

Thanks,

Jeff & Chris
Jeff Tantsura | 3 Aug 05:13 2015
Picon

RTGWG adoption call for draft-shaikh-rtgwg-policy-model

Hi RTGWG,

The authors have requested the RTGWG to adopt
draft-shaikh-rtgwg-policy-model

Please indicate support or no-support by August 18, 2015.

If you are listed as a document author or contributor please respond to
this email stating of whether or not you are aware of any relevant IPR.
The response needs to be sent to the RTGWG mailing list. The document will
not advance to the next stage until a response has been received from each
author and each individual that has contributed to the document.

Thanks,

Jeff & Chris
Jeff Tantsura | 3 Aug 05:08 2015
Picon

RTGWG adoption call for draft-liu-rtgwg-yang-rip-01

Hi RTGWG,

The RTGWG adoption call for draft-liu-rtgwg-yang-rip-01 has been
completed, and this document has been adopted as a WG draft.
The authors should submit this as draft-ietf-rtgwg-yang-rip-00.txt.

Cheers,
Jeff & Chris	
internet-drafts | 31 Jul 17:41 2015
Picon

I-D Action: draft-ietf-rtgwg-bgp-routing-large-dc-05.txt


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

        Title           : Use of BGP for routing in large-scale data centers
        Authors         : Petr Lapukhov
                          Ariff Premji
                          Jon Mitchell
	Filename        : draft-ietf-rtgwg-bgp-routing-large-dc-05.txt
	Pages           : 34
	Date            : 2015-07-31

Abstract:
   Some network operators build and operate data centers that support
   over one hundred thousand servers.  In this document, such data
   centers are referred to as "large-scale" to differentiate them from
   smaller infrastructures.  Environments of this scale have a unique
   set of network requirements with an emphasis on operational
   simplicity and network stability.  This document summarizes
   operational experience in designing and operating large-scale data
   centers using BGP as the only routing protocol.  The intent is to
   report on a proven and stable routing design that could be leveraged
   by others in the industry.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-bgp-routing-large-dc/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-rtgwg-bgp-routing-large-dc-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-bgp-routing-large-dc-05

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Gmane