Should this draft address the issue (sending and receiving side) that a rtr might temporarily be unable to perform origin validation (e.g., reboot, has not synched with cache yet, ... )?
I suppose absence of the community at all is a signal that the sender did not attempt validation ... Maybe the text for receiving should address the possibility that you support this draft, but receive an IBGP update that does not include this community? dougm -- Doug Montgomery Mgr. Internet & Scalable Systems Research / ITL / NIST On 8/3/11 1:41 AM, "[email protected]" <[email protected]> wrote: >A New Internet-Draft is available from the on-line Internet-Drafts >directories. This draft is a work item of the Secure Inter-Domain Routing >Working Group of the IETF. > > Title : BGP Prefix Origin Validation State Extended Community > Author(s) : Pradosh Mohapatra > Keyur Patel > John Scudder > David Ward > Randy Bush > Filename : draft-ietf-sidr-origin-validation-signaling-01.txt > Pages : 7 > Date : 2011-08-02 > > As part of the origination AS validation process, it can be desirable > to automatically consider the validation state of routes in the BGP > decision process. The purpose of this document is to provide a > specification for doing so. The document also defines a new BGP > opaque extended community to carry the validation state inside an > autonomous system to influence the decision process of the IBGP > speakers. > > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-sidr-origin-validation-sign >aling-01.txt > >Internet-Drafts are also available by anonymous FTP at: >ftp://ftp.ietf.org/internet-drafts/ > >This Internet-Draft can be retrieved at: >ftp://ftp.ietf.org/internet-drafts/draft-ietf-sidr-origin-validation-signa >ling-01.txt >_______________________________________________ >sidr mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/sidr _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
