1 / 4

draft-ietf-sidr-bgpsec-ops-02 diffs from -00 (Jul)

draft-ietf-sidr-bgpsec-ops-02 diffs from -00 (Jul). sidr / IETF Taipei 2011.11.15 Randy Bush < randy @ psg.com>. Fetch From Upstream.

cissy
Download Presentation

draft-ietf-sidr-bgpsec-ops-02 diffs from -00 (Jul)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-ietf-sidr-bgpsec-ops-02diffs from -00 (Jul) sidr / IETF Taipei 2011.11.15 Randy Bush <randy@psg.com>

  2. Fetch From Upstream A transit provider or a network with peers SHOULD validate NLRI in announcements made by upstreams, downstreams, and peers. They still SHOULD trustTo minimize impact on the global RPKI, they SHOULD fetch from and then revalidate data from caches provided by their upstreams.

  3. Transparent RSs If it is known that a BGPsec neighbor is not a transparent route server, and the router provides a knob to disallow a received pCount (prepend count, zero for transparent route servers) of zero, that knob SHOULD be applied.

  4. Confederation To prevent exposure of the internals of BGP Confederations [RFC5065], a BGPsec speaker which is a Member-AS of a Confederation MUST NOT sign updates sent to another Member-AS of the same Confederation. JGS has a better formulation!

More Related