headers
UTTARO, JAMES, ATTLABS | 1 Dec 15:21
Picon
Favicon

Re: draft-walton-bgp-add-paths-06.txt as IDR WG document

Support.

Jim Uttaro 

-----Original Message-----
From: idr-bounces <at> ietf.org [mailto:idr-bounces <at> ietf.org] On Behalf Of
John G. Scudder
Sent: Monday, November 24, 2008 2:44 PM
To: Yakov Rekhter; skh <at> ghs.com
Cc: Inter-Domain Routing List
Subject: [Idr] draft-walton-bgp-add-paths-06.txt as IDR WG document

The authors would like to request that draft-walton-bgp-add- 
paths-06.txt be adopted as an IDR WG document.

Thanks,

--John
_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr
_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr
Permalink | Reply | 1 comment |
headers
HENDERICKX Wim | 1 Dec 18:24
Picon

Re: draft-walton-bgp-add-paths-06.txt as IDR WG document

support 

-----Original Message-----
From: idr-bounces <at> ietf.org [mailto:idr-bounces <at> ietf.org] On Behalf Of
UTTARO, JAMES, ATTLABS
Sent: maandag 1 december 2008 15:21
To: John G. Scudder; Yakov Rekhter; skh <at> ghs.com
Cc: Inter-Domain Routing List
Subject: Re: [Idr] draft-walton-bgp-add-paths-06.txt as IDR WG document

Support.

Jim Uttaro 

-----Original Message-----
From: idr-bounces <at> ietf.org [mailto:idr-bounces <at> ietf.org] On Behalf Of
John G. Scudder
Sent: Monday, November 24, 2008 2:44 PM
To: Yakov Rekhter; skh <at> ghs.com
Cc: Inter-Domain Routing List
Subject: [Idr] draft-walton-bgp-add-paths-06.txt as IDR WG document

The authors would like to request that draft-walton-bgp-add-
paths-06.txt be adopted as an IDR WG document.

Thanks,

--John
_______________________________________________
Idr mailing list
(Continue reading)

Permalink | Reply | 0 comments |
headers
bruno.decraene | 3 Dec 17:36

Re: draft-walton-bgp-add-paths-06.txt as IDR WG document

Support.

> -----Message d'origine-----
> De : idr-bounces <at> ietf.org [mailto:idr-bounces <at> ietf.org] De la part de Yakov Rekhter
> Envoyé : lundi 24 novembre 2008 20:51
> À : idr <at> ietf.org
> Objet : [Idr] draft-walton-bgp-add-paths-06.txt as IDR WG document
> 
> Folks,
> 
> Please send your comments on the attached. The deadline for comments
> is Dec 12, 2008.
> 
> Yakov.
> ------- Forwarded Message
> 
> Date:    Mon, 24 Nov 2008 14:44:00 -0500
> From:    "John G. Scudder" <jgs <at> juniper.net>
> To:      Yakov Rekhter <yakov <at> juniper.net>, skh <at> ghs.com
> cc:      Inter-Domain Routing List <idr <at> ietf.org>
> Subject: draft-walton-bgp-add-paths-06.txt as IDR WG document
> 
> The authors would like to request that draft-walton-bgp-add-
> paths-06.txt be adopted as an IDR WG document.
> 
> Thanks,
> 
> - --John
> 
> ------- End of Forwarded Message
(Continue reading)

Permalink | Reply | 0 comments |
headers
Uli Bornhauser | 4 Dec 10:15
Picon
Favicon
Gravatar

Re: draft-walton-bgp-add-paths-06.txt as IDR WG document

Hi Robert,

here should be a simple example for the problem regarding Add-path, Best
/ Second Best, and Border Router Attr Set I mentioned:

-------------------------------------

---------+        RR        +--------
      ASx|   d1 .    . d1   |ASy
         |     .      .     |
 R-ID.6.....C-ID.5  C-ID.8.....R-ID.2
     q1->|    .        .    |<-q2
         |    .        .    |
---------+    .        .    +--------
              .        .
         MED2 .        . MED1
       +------.--------.----+
       |ASz p1.        .p2  |
       |      .        .    |
       |   R-ID.3    R-ID.9 |

-------------------------------------
q1, q2, p1, p2: Paths advertised from neighboring systems.
     R: Routers in neighboring systems, Route Reflector or Clients
     C: Client in own System
    RR: Route Reflector in own System
*-ID.x: Router has BGP ID .x
    d1: Links with a distance of 1
   ASa: AS with ID a
(Continue reading)

Permalink | Reply | 4 comments |
headers
Robert Raszuk | 4 Dec 12:29
Favicon

Re: draft-walton-bgp-add-paths-06.txt as IDR WG document

Hi Uli,

 > Client C-ID.5 receives the paths q1 and p1.

This is already not the correct observation. In the correct architecture 
of this network (no misconfiguration) C-ID.5 would receive all 4 paths. 
Therefor p2 will win.

Cheers,
R.

> Hi Robert,
> 
> here should be a simple example for the problem regarding Add-path, Best
> / Second Best, and Border Router Attr Set I mentioned:
> 
> -------------------------------------
> 
> ---------+        RR        +--------
>       ASx|   d1 .    . d1   |ASy
>          |     .      .     |
>  R-ID.6.....C-ID.5  C-ID.8.....R-ID.2
>      q1->|    .        .    |<-q2
>          |    .        .    |
> ---------+    .        .    +--------
>               .        .
>          MED2 .        . MED1
>        +------.--------.----+
>        |ASz p1.        .p2  |
>        |      .        .    |
(Continue reading)

Permalink | Reply | 3 comments |
headers
Uli Bornhauser | 4 Dec 13:30
Picon
Favicon
Gravatar

Re: draft-walton-bgp-add-paths-06.txt as IDR WG document

Hi Robert,

I think I did not get your point yet. Why do you think that a
misconfiguration is needed for the example?
Client C-ID.5 keeps two eBGP sessions (to R-ID.6 and R-ID.3) and thus
receives q1 and p1. Client C-ID.8 also holds two external sessions (to
R-ID.9 and R-ID.2) and receives p2 and q2. The Route Reflector of
clients C-ID.5 and C-ID.8 receives all paths, and re-advertises its
first and second best (which are q1 and q2).
Thus, client C-ID.5 is provided with q1, q2, and p1. Knowing q2 has no
effect on its routing decision. Path p2 is not visible at C-ID.5 at all.

Can you please explain I detail from where client C-ID.5 should learn
path p2?

Thank you and Regards

Uli

Robert Raszuk schrieb:
> Hi Uli,
>
> > Client C-ID.5 receives the paths q1 and p1.
>
> This is already not the correct observation. In the correct
> architecture of this network (no misconfiguration) C-ID.5 would
> receive all 4 paths. Therefor p2 will win.
>
> Cheers,
> R.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Robert Raszuk | 4 Dec 13:36
Favicon

Re: draft-walton-bgp-add-paths-06.txt as IDR WG document

Hi Uli,

I was assuming that RR would advertise all paths not just best and 
second best.

But you are in general very correct that regardless of what RR 
propagates via IBGP domain the rtr_id of the advertising peer is still 
subject to be compared before the attr_set hence we have an issue.

In full mesh ibgp that would not be the problem, but in the RR case it 
still  think is.

I propose we talk offline and try to come up together on the best 
solution considering your work already in this space.

Cheers,
R.

> Hi Robert,
> 
> I think I did not get your point yet. Why do you think that a
> misconfiguration is needed for the example?
> Client C-ID.5 keeps two eBGP sessions (to R-ID.6 and R-ID.3) and thus
> receives q1 and p1. Client C-ID.8 also holds two external sessions (to
> R-ID.9 and R-ID.2) and receives p2 and q2. The Route Reflector of
> clients C-ID.5 and C-ID.8 receives all paths, and re-advertises its
> first and second best (which are q1 and q2).
> Thus, client C-ID.5 is provided with q1, q2, and p1. Knowing q2 has no
> effect on its routing decision. Path p2 is not visible at C-ID.5 at all.
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Danny McPherson | 5 Dec 17:26

Re: draft-walton-bgp-add-paths-06.txt as IDR WG document


On Dec 4, 2008, at 5:36 AM, Robert Raszuk wrote:

> Hi Uli,
>
> I was assuming that RR would advertise all paths not just best and  
> second best.
>
> But you are in general very correct that regardless of what RR  
> propagates via IBGP domain the rtr_id of the advertising peer is  
> still subject to be compared before the attr_set hence we have an  
> issue.
>
> In full mesh ibgp that would not be the problem, but in the RR case  
> it still  think is.
>
> I propose we talk offline and try to come up together on the best  
> solution considering your work already in this space.

As an aside, this is another reason why comparing MEDs
for a prefix with paths learned from different ASes is
a bad idea.

-danny
_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr
(Continue reading)

Permalink | Reply | 0 comments |
headers
Yakov Rekhter | 9 Dec 15:45
Favicon

draft-jakma-mrai-dep-00 (fwd)

Folks,

While we received no objections for accepting draft-jakma-mrai-dep-00
as an IDR WG document, we did not receive sufficient support either.

If you think this document should be accepted as an IDR WG document,
please reply to this e-mail *before Dec 12, 2008*.

Yakov.
------- Forwarded Message

Date:    Tue, 25 Nov 2008 15:29:29 -0800
From:    Yakov Rekhter <yakov <at> juniper.net>
To:      idr <at> ietf.org
Subject: [Idr] draft-jakma-mrai-dep-00 (fwd)

Folks,

Please send your comments on the attached. The deadline for comments
is Dec 12, 2008.

Yakov.
- ------- Forwarded Message

Date:    Tue, 25 Nov 2008 23:14:49 +0000
From:    Paul Jakma <Paul.Jakma <at> Sun.COM>
To:      Inter-Domain Routing List <idr <at> ietf.org>
cc:      paul <at> jakma.org
Subject: [Idr] draft-jakma-mrai-dep-00 (fwd)
(Continue reading)

Permalink | Reply | 7 comments |
headers
John Leslie | 9 Dec 16:56
Favicon

Re: draft-jakma-mrai-dep-00 (fwd)

Yakov Rekhter <yakov <at> juniper.net> wrote:
> 
> While we received no objections for accepting draft-jakma-mrai-dep-00
> as an IDR WG document, we did not receive sufficient support either.
> 
> If you think this document should be accepted as an IDR WG document,
> please reply to this e-mail *before Dec 12, 2008*.

   I definitely support Paul on the essence of the document.

   I do not believe we should wait on every jot and tittle before adopting
it as a WG document.

--
John Leslie <john <at> jlc.net>
_______________________________________________
Idr mailing list
Idr <at> ietf.org
https://www.ietf.org/mailman/listinfo/idr
Permalink | Reply | 0 comments |

Gmane