Re: [Lsr] WG Adoption Call for "IS-IS Routing for Spine-Leaf Topology" - draft-shen-isis-spine-leaf-ext-07

[Ayan Banerjee]

Support.

Thanks,
Ayan

On Sat, Dec 1, 2018 at 4:54 PM Acee Lindem (acee)  wrote:

> This begins a two-week WG adoption call for the subject draft. As anyone
> who has been following the topic knows, there are a lot of proposal in this
> space. However, as WG co-chair, I believe this simple IS-IS extension
> doesn’t really conflict with any of the other more disruptive flooding
> proposals. Also, it is more mature and there is some implementation
> momentum. Note that I’m making every attempt to be transparent and it is
> perfectly ok to disagree with me. Please post your comments to this list
> before 12:00 AM, December 16th, 2018.
>
>
>
> With respect to the more disruptive proposals, we are discussing our next
> steps.
>
>
>
> Thanks,
>
> Acee
> ___
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] WG Adoption Call for "IS-IS Routing for Spine-Leaf Topology" - draft-shen-isis-spine-leaf-ext-07

[Mankamana Mishra (mankamis)]

Support .

Sent from my iPhone

On Dec 1, 2018, at 16:55, Acee Lindem (acee) 
mailto:a...@cisco.com>> wrote:

This begins a two-week WG adoption call for the subject draft. As anyone who 
has been following the topic knows, there are a lot of proposal in this space. 
However, as WG co-chair, I believe this simple IS-IS extension doesn’t really 
conflict with any of the other more disruptive flooding proposals. Also, it is 
more mature and there is some implementation momentum. Note that I’m making 
every attempt to be transparent and it is perfectly ok to disagree with me. 
Please post your comments to this list before 12:00 AM, December 16th, 2018.

With respect to the more disruptive proposals, we are discussing our next steps.

Thanks,
Acee
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] WG Adoption Call for "IS-IS Routing for Spine-Leaf Topology" - draft-shen-isis-spine-leaf-ext-07

[Nagendra Kumar Nainar (naikumar)]

Hi,

Support.

Regards,
Nagendra

On Sat, Dec 1, 2018 at 7:55 PM Acee Lindem (acee)  wrote:
>
> This begins a two-week WG adoption call for the subject draft. As anyone 
who has been following the topic knows, there are a lot of proposal in this 
space. However, as WG co-chair, I believe this simple IS-IS extension doesn’t 
really conflict with any of the other more disruptive flooding proposals. Also, 
it is more mature and there is some implementation momentum. Note that I’m 
making every attempt to be transparent and it is perfectly ok to disagree with 
me. Please post your comments to this list before 12:00 AM, December 16th, 2018.
>
>
>
> With respect to the more disruptive proposals, we are discussing our next 
steps.
>
>
>
> Thanks,
>
> Acee
>
> ___
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr

___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr


___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] WG Adoption Call for "IS-IS Routing for Spine-Leaf Topology" - draft-shen-isis-spine-leaf-ext-07

[Naiming Shen (naiming)]

Support as a co-author.

thanks.
- Naiming

On Dec 1, 2018, at 4:54 PM, Acee Lindem (acee) 
mailto:a...@cisco.com>> wrote:

This begins a two-week WG adoption call for the subject draft. As anyone who 
has been following the topic knows, there are a lot of proposal in this space. 
However, as WG co-chair, I believe this simple IS-IS extension doesn’t really 
conflict with any of the other more disruptive flooding proposals. Also, it is 
more mature and there is some implementation momentum. Note that I’m making 
every attempt to be transparent and it is perfectly ok to disagree with me. 
Please post your comments to this list before 12:00 AM, December 16th, 2018.

With respect to the more disruptive proposals, we are discussing our next steps.

Thanks,
Acee
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] WG Adoption Call for "IS-IS Routing for Spine-Leaf Topology" - draft-shen-isis-spine-leaf-ext-07

[Mohan Nanduri]

Support.

Cheers,
-Mohan
On Sat, Dec 1, 2018 at 7:55 PM Acee Lindem (acee)  wrote:
>
> This begins a two-week WG adoption call for the subject draft. As anyone who 
> has been following the topic knows, there are a lot of proposal in this 
> space. However, as WG co-chair, I believe this simple IS-IS extension doesn’t 
> really conflict with any of the other more disruptive flooding proposals. 
> Also, it is more mature and there is some implementation momentum. Note that 
> I’m making every attempt to be transparent and it is perfectly ok to disagree 
> with me. Please post your comments to this list before 12:00 AM, December 
> 16th, 2018.
>
>
>
> With respect to the more disruptive proposals, we are discussing our next 
> steps.
>
>
>
> Thanks,
>
> Acee
>
> ___
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr

___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] WG Adoption Call for "IS-IS Routing for Spine-Leaf Topology" - draft-shen-isis-spine-leaf-ext-07

[Jeff Tantsura]

Yes/support

Regards,
Jeff

> On Dec 1, 2018, at 16:54, Acee Lindem (acee)  wrote:
> 
> This begins a two-week WG adoption call for the subject draft. As anyone who 
> has been following the topic knows, there are a lot of proposal in this 
> space. However, as WG co-chair, I believe this simple IS-IS extension doesn’t 
> really conflict with any of the other more disruptive flooding proposals. 
> Also, it is more mature and there is some implementation momentum. Note that 
> I’m making every attempt to be transparent and it is perfectly ok to disagree 
> with me. Please post your comments to this list before 12:00 AM, December 
> 16th, 2018.
>  
> With respect to the more disruptive proposals, we are discussing our next 
> steps.
>  
> Thanks,
> Acee
> ___
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

[Lsr] FW: New Version Notification for draft-ginsberg-lsr-isis-invalid-tlv-01.txt

[Les Ginsberg (ginsberg)]

FYI -

This new version includes some new co-authors, adds some clarifying text, and 
corrects an error found in RFC 6232.

   Les


-Original Message-
From: internet-dra...@ietf.org  
Sent: Sunday, December 02, 2018 9:03 AM
To: Shraddha Hegde ; Tony Przygienda ; 
Paul Wells (pauwells) ; Tony Li ; Les 
Ginsberg (ginsberg) 
Subject: New Version Notification for draft-ginsberg-lsr-isis-invalid-tlv-01.txt


A new version of I-D, draft-ginsberg-lsr-isis-invalid-tlv-01.txt
has been successfully submitted by Les Ginsberg and posted to the
IETF repository.

Name:   draft-ginsberg-lsr-isis-invalid-tlv
Revision:   01
Title:  Invalid TLV Handling in IS-IS
Document date:  2018-12-02
Group:  Individual Submission
Pages:  8
URL:
https://www.ietf.org/internet-drafts/draft-ginsberg-lsr-isis-invalid-tlv-01.txt
Status: 
https://datatracker.ietf.org/doc/draft-ginsberg-lsr-isis-invalid-tlv/
Htmlized:   
https://tools.ietf.org/html/draft-ginsberg-lsr-isis-invalid-tlv-01
Htmlized:   
https://datatracker.ietf.org/doc/html/draft-ginsberg-lsr-isis-invalid-tlv
Diff:   
https://www.ietf.org/rfcdiff?url2=draft-ginsberg-lsr-isis-invalid-tlv-01

Abstract:
   Key to the extensibility of the Intermediate System to Intermediate
   System (IS-IS) protocol has been the handling of unsupported and/or
   invalid Type/Length/Value (TLV) tuples.  Although there are explicit
   statements in existing specifications, in some cases the expected
   behavior is "well known" but not explicitly stated.

   This document discusses the "well known behaviors" and makes them
   explicit in order to insure that interoperability is maximized.

   This document when approved updates RFC3563, RFC5305, RFC6232, and
   RFC6233.



  


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

___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] WG Adoption Call for "IS-IS Routing for Spine-Leaf Topology" - draft-shen-isis-spine-leaf-ext-07

[Yingzhen Qu]

Support.

Thanks,
Yingzhen

From: Lsr  on behalf of Hannes Gredler 
Date: Sunday, December 2, 2018 at 7:46 AM
To: "Acee Lindem (acee)" 
Cc: "lsr@ietf.org" 
Subject: Re: [Lsr] WG Adoption Call for "IS-IS Routing for Spine-Leaf Topology" 
- draft-shen-isis-spine-leaf-ext-07

support

On 02.12.2018, at 01:54, Acee Lindem (acee) 
mailto:a...@cisco.com>> wrote:
This begins a two-week WG adoption call for the subject draft. As anyone who 
has been following the topic knows, there are a lot of proposal in this space. 
However, as WG co-chair, I believe this simple IS-IS extension doesn’t really 
conflict with any of the other more disruptive flooding proposals. Also, it is 
more mature and there is some implementation momentum. Note that I’m making 
every attempt to be transparent and it is perfectly ok to disagree with me. 
Please post your comments to this list before 12:00 AM, December 16th, 2018.

With respect to the more disruptive proposals, we are discussing our next steps.

Thanks,
Acee
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] WG Adoption Call for "IS-IS Routing for Spine-Leaf Topology" - draft-shen-isis-spine-leaf-ext-07

[Hannes Gredler]

support

> On 02.12.2018, at 01:54, Acee Lindem (acee)  wrote:
> 
> This begins a two-week WG adoption call for the subject draft. As anyone who 
> has been following the topic knows, there are a lot of proposal in this 
> space. However, as WG co-chair, I believe this simple IS-IS extension doesn’t 
> really conflict with any of the other more disruptive flooding proposals. 
> Also, it is more mature and there is some implementation momentum. Note that 
> I’m making every attempt to be transparent and it is perfectly ok to disagree 
> with me. Please post your comments to this list before 12:00 AM, December 
> 16th, 2018.
>  
> With respect to the more disruptive proposals, we are discussing our next 
> steps.
>  
> Thanks,
> Acee
> ___
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] WG Adoption Call for "IS-IS Routing for Spine-Leaf Topology" - draft-shen-isis-spine-leaf-ext-07

[Peter Psenak]

Support.

Peter

On 02/12/18 01:54 , Acee Lindem (acee) wrote:

This begins a two-week WG adoption call for the subject draft. As anyone
who has been following the topic knows, there are a lot of proposal in
this space. However, as WG co-chair, I believe this simple IS-IS
extension doesn’t really conflict with any of the other more disruptive
flooding proposals. Also, it is more mature and there is some
implementation momentum. Note that I’m making every attempt to be
transparent and it is perfectly ok to disagree with me. Please post your
comments to this list before 12:00 AM, December 16^th , 2018.

With respect to the more disruptive proposals, we are discussing our
next steps.

Thanks,

Acee



___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr



___
Lsr mailing list
Lsr@ietf.org
https://www.ietf.org/mailman/listinfo/lsr