+1 to Rob's comment here
Just because use cases come along while another draft is in flight
shouldn't mean you have to loop back to the initial draft. If this was
the case, you're prolonging an already lengthy process. There are
likely many more to come in the future that have not been thought
ietf.org;
> Anil Kumar S N (VRP Network BL)
> Cc: spring@ietf.org
> Subject: Re: [spring] draft-ietf-spring-segment-routing-05
>
> +1 to Rob's comment here
>
> Just because use cases come along while another draft is in flight
> shouldn't mean you have to loop back to th
Totally agree
We expect lots of applications and use cases to come.
Let's close this document
Ahmed
On 9/25/2015 1:22 AM, Rob Shakir wrote:
On 24 September 2015 at 09:09:00, Anil Kumar S N (VRP Network BL)
(anil...@huawei.com) wrote:
Hi Rob,
Thanks for reverting back the mail.
If
I agree.
s.
On Sep 25, 2015, at 10:22 AM, Rob Shakir wrote:
>
> On 24 September 2015 at 09:09:00, Anil Kumar S N (VRP Network BL)
> (anil...@huawei.com) wrote:
>> Hi Rob,
>>
>> Thanks for reverting back the mail.
>>
>> If there is a desire to control traffic flows on
On 24 September 2015 at 09:09:00, Anil Kumar S N (VRP Network BL)
(anil...@huawei.com) wrote:
> Hi Rob,
>
> Thanks for reverting back the mail.
>
> If there is a desire to control traffic flows on individual bundle interface,
> information about each of the bundle members interface is
umar S N
> (VRP Network BL)
> Cc: spring@ietf.org
> Subject: Re: [spring] draft-ietf-spring-segment-routing-05
>
> Anil,
>
> Thanks for the mail.
>
> On September 23, 2015 at 02:19:54, Anil Kumar S N (VRP Network BL)
> (anil...@huawei.com) wrote:
> > 3.5.3. Bundle
Anil,
Thanks for the mail.
On September 23, 2015 at 02:19:54, Anil Kumar S N (VRP Network BL)
(anil...@huawei.com) wrote:
> 3.5.3. Bundle Adjacency Segments
>
> A number of physical interfaces can be bundled to be a
> a logical interface. Adj-SIDs can be used in order to represent individual