Re: [GROW] [Idr] WG LC for Extended BGP Administrative Shutdown Communication (bs) - draft-ietf-idr-rfc8203bis-04.txt (7/9 to 7/23) - extended to 8/6/2019

2019-08-07 Thread Susan Hares
Greetings: 

 

The IDR WG had reached consensus on draft-ietf-idr-rfc8203bis-04.txt, and it
has past WG LC.  

 

The authors should post the following:  

1)  draft-ietf-idr-rfc8203bis-05.txt - with the proposed changes,

2)  make any updates to the IDR Wiki page with implementation
information 

https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-rfc8203bis

 

After these items are posted, the shepherd (Susan Hares) will write-up the
shepherd report and send it to the IESG for publications. 

 

Cheerily, Susan Hares 

 

 

From: Susan Hares [mailto:sha...@ndzh.com] 
Sent: Thursday, July 25, 2019 5:25 PM
To: grow@ietf.org
Subject: FW: [Idr] WG LC for Extended BGP Administrative Shutdown
Communication (bs) - draft-ietf-idr-rfc8203bis-04.txt (7/9 to 7/23) -
extended to 8/6/2019 

 

Greetings: 

 

IDR has extended its WG LC for draft-ietf-idr-rfc8203bis-04.txt  until
8/6/2019. 

 

Since this draft has operational impact, perhaps you'd like to consider
providing your opinion on this draft.   

 

Or if you are an IDR participant, you can go to the IDR list and comment
during this extended WG LC. 

 

Cheerily, Susan Hares 

 

From: Idr [mailto:idr-boun...@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, July 9, 2019 9:13 AM
To: 'idr wg'
Subject: [Idr] WG LC for Extended BGP Administrative Shutdown Communication
(bs) - draft-ietf-idr-rfc8203bis-04.txt (7/9 to 7/23)

 

This begins a 2 week WG last call for draft-ietf-idr-rfc8203bis-04.txt from
July 9, 2019 to July 23, 2019. . 

 

Please consider if you believe this revision of RFC8203 (Administrative
Shutdown)

a)  Will benefit operational networks,

b)  is technically complete, and 

c)   ready for publication. 

 

In your comments, please indicate whether you "support" or "do not support"
its publication. 

 

This draft contains IPR notice that causes "IPR warnings".   The authors
believe that this text is automatically generated by the IETF tools and the
warning is not appropriate.   

 

As the shepherd, I am  investigating this issue.   If you have specific
knowledge on this issue, you may send it to the list or to me directly. 

 

Cheerily, Susan Hares 

 

 

___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow


Re: [GROW] [Idr] WG LC for Extended BGP Administrative Shutdown Communication (bs) - draft-ietf-idr-rfc8203bis-04.txt (7/9 to 7/23) - Extended to 8/6/2019

2019-07-26 Thread Acee Lindem (acee)
I also support publication.
Thanks
Acee

From: Idr  on behalf of Jeff Tantsura 

Date: Thursday, July 25, 2019 at 5:49 PM
To: IDR List , Susan Hares 
Cc: "grow@ietf.org" 
Subject: Re: [Idr] WG LC for Extended BGP Administrative Shutdown Communication 
(bs) - draft-ietf-idr-rfc8203bis-04.txt (7/9 to 7/23) - Extended to 8/6/2019

Sue,

I support publication of this draft.

Cheers,
Jeff
On Jul 25, 2019, 5:26 PM -0400, Susan Hares , wrote:

Greetings IDR:

The IDR WG call for input on draft-ietf-idr-rfc8203bis-04.txt has received only 
2 comments.  Since this is a draft that updates an operationally needed 
feature,  I am extending the WG LC until 8/6/2019.

If you believe this draft is ready for publication, please respond to this WG 
LC.

Sue Hares

From: Idr [mailto:idr-boun...@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, July 9, 2019 9:13 AM
To: 'idr wg'
Subject: [Idr] WG LC for Extended BGP Administrative Shutdown Communication 
(bs) - draft-ietf-idr-rfc8203bis-04.txt (7/9 to 7/23)

This begins a 2 week WG last call for draft-ietf-idr-rfc8203bis-04.txt from 
July 9, 2019 to July 23, 2019. .

Please consider if you believe this revision of RFC8203 (Administrative 
Shutdown)

Will benefit operational networks,

is technically complete, and

ready for publication.

In your comments, please indicate whether you “support” or “do not support” its 
publication.

This draft contains IPR notice that causes “IPR warnings”.   The authors 
believe that this text is automatically generated by the IETF tools and the 
warning is not appropriate.

As the shepherd, I am  investigating this issue.   If you have specific 
knowledge on this issue, you may send it to the list or to me directly.

Cheerily, Susan Hares


___
Idr mailing list
i...@ietf.org
https://www.ietf.org/mailman/listinfo/idr
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow


Re: [GROW] [Idr] WG LC for Extended BGP Administrative Shutdown Communication (bs) - draft-ietf-idr-rfc8203bis-04.txt (7/9 to 7/23) - Extended to 8/6/2019

2019-07-25 Thread John Scudder
(As an individual contributor and co-author.)

Thanks for extending this, Sue. Maybe it will help the WG to have a reminder 
about what this document does. 

It’s a revision of RFC 8203. First, here is the rfcdiff vs. RFC 8203: 
http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=rfc8203=draft-ietf-idr-rfc8203bis
It is quite short, especially when you skip over the boilerplate and "RFC 
EDITOR: REMOVE BEFORE PUBLICATION” sections. 

The sole normative change vs. 8203 is the deletion of one sentence:

OLD:
   Length:  this 8-bit field represents the length of the Shutdown
  Communication field in octets.  The length value MUST range from 0
  to 128 inclusive.  When the length value is zero, no Shutdown
  Communication field follows.
NEW:
   Length:  this 8-bit field represents the length of the Shutdown
  Communication field in octets.  When the length value is zero, no
  Shutdown Communication field follows.

The reason for this change is summarized in in Appendix B:

   Feedback from operators based in regions which predominantly use
   multibyte character sets, showed that messages similar in meaning to
   what can be send in other languages in using single-byte encoding,
   failed to fit within the Length constraints as specified by
   [RFC8203].  For example, the phrase: 'Planned work to add switch to
   stack.  Completion time - 30 minutes' has length 65 bytes.  Its
   translation in Russian
   '
 
   86; 

Re: [GROW] [Idr] WG LC for Extended BGP Administrative Shutdown Communication (bs) - draft-ietf-idr-rfc8203bis-04.txt (7/9 to 7/23) - Extended to 8/6/2019

2019-07-25 Thread Jeff Tantsura
Sue,

I support publication of this draft.

Cheers,
Jeff
On Jul 25, 2019, 5:26 PM -0400, Susan Hares , wrote:
> Greetings IDR:
>
> The IDR WG call for input on draft-ietf-idr-rfc8203bis-04.txt has received 
> only 2 comments.  Since this is a draft that updates an operationally needed 
> feature,  I am extending the WG LC until 8/6/2019.
>
> If you believe this draft is ready for publication, please respond to this WG 
> LC.
>
> Sue Hares
>
> From: Idr [mailto:idr-boun...@ietf.org] On Behalf Of Susan Hares
> Sent: Tuesday, July 9, 2019 9:13 AM
> To: 'idr wg'
> Subject: [Idr] WG LC for Extended BGP Administrative Shutdown Communication 
> (bs) - draft-ietf-idr-rfc8203bis-04.txt (7/9 to 7/23)
>
> This begins a 2 week WG last call for draft-ietf-idr-rfc8203bis-04.txt from 
> July 9, 2019 to July 23, 2019. .
>
> Please consider if you believe this revision of RFC8203 (Administrative 
> Shutdown)
> Will benefit operational networks,
> is technically complete, and
> ready for publication.
>
> In your comments, please indicate whether you “support” or “do not support” 
> its publication.
>
> This draft contains IPR notice that causes “IPR warnings”..   The authors 
> believe that this text is automatically generated by the IETF tools and the 
> warning is not appropriate.
>
> As the shepherd, I am  investigating this issue.   If you have specific 
> knowledge on this issue, you may send it to the list or to me directly.
>
> Cheerily, Susan Hares
>
>
> ___
> Idr mailing list
> i...@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow


Re: [GROW] [Idr] WG LC for Extended BGP Administrative Shutdown Communication (bs) - draft-ietf-idr-rfc8203bis-04.txt (7/9 to 7/23) - Extended to 8/6/2019

2019-07-25 Thread Susan Hares
Greetings IDR: 

 

The IDR WG call for input on draft-ietf-idr-rfc8203bis-04.txt has received
only 2 comments.  Since this is a draft that updates an operationally needed
feature,  I am extending the WG LC until 8/6/2019.  

 

If you believe this draft is ready for publication, please respond to this
WG LC. 

 

Sue Hares 

 

From: Idr [mailto:idr-boun...@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, July 9, 2019 9:13 AM
To: 'idr wg'
Subject: [Idr] WG LC for Extended BGP Administrative Shutdown Communication
(bs) - draft-ietf-idr-rfc8203bis-04.txt (7/9 to 7/23)

 

This begins a 2 week WG last call for draft-ietf-idr-rfc8203bis-04.txt from
July 9, 2019 to July 23, 2019. . 

 

Please consider if you believe this revision of RFC8203 (Administrative
Shutdown)

a)  Will benefit operational networks,

b)  is technically complete, and 

c)   ready for publication. 

 

In your comments, please indicate whether you "support" or "do not support"
its publication. 

 

This draft contains IPR notice that causes "IPR warnings".   The authors
believe that this text is automatically generated by the IETF tools and the
warning is not appropriate.   

 

As the shepherd, I am  investigating this issue.   If you have specific
knowledge on this issue, you may send it to the list or to me directly. 

 

Cheerily, Susan Hares 

 

 

___
GROW mailing list
GROW@ietf.org
https://www.ietf.org/mailman/listinfo/grow