[Idr] WG LC for draft-ietf-idr-deprecate-as-set-confed-set-14 (7/8 to 7/

[Susan Hares <[e-mail]>]

This begins a 2 week WG LC for
draft-ietf-idr-deprecate-as-set-confed-set-14.txt
https://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-as-set-confed-set/

All authors should respond to this email with an IPR statement.

Here is a short summary of why this document is:

   BCP 172 (i.e., RFC 6472) recommends not using AS_SET and
   AS_CONFED_SET AS_PATH segment types in the Border Gateway Protocol
   (BGP).  This document advances that recommendation to a standards
   requirement in BGP; it proscribes the use of the AS_SET and
   AS_CONFED_SET path segment types in the AS_PATH.

FYI the verb proscribe means:

  1.  forbid, especially by law.
  2.  denounce or condemn.

It is a complex English word, but it fits the document.
One similar word is "prohibit".

Questions to consider in your comments:


  1.  Is now the time to proscribe AS_SETs and

AS-CONF_SET path segments types in AS_PATH?


  1.  Is the document clear and ready for standardization?

    Both Keyur and I wrote shepherd reports,
    so we'll post a joint shepherd report.

    Our comments focus on the clarity of the document.


  1.  Does this help BGP security in the network?


Cheers, Sue