thanks for the review!
- whether it's intended or 'safe' to use BGP Attributes, (MED, communities),
to convey validity of prefixes from one ASN to another ASN
what is valid for you may not be valid for me, see draft-ietf-sidr-ltamgmt.
- better guidance/recommendations around the number,
On Oct 30, 2011, at 6:57 AM, Randy Bush wrote:
note that the RIRs were talking 24 hour publication cycles, last i heard
(long ago, i admit). [ i thought this was nutso ] so a lot of this has
yet to play out.
I see 4-6 hours in the document, but what do you really think is
reasonable
I have read this document and think it should be published as a standards-track
RFC. It is fairly complex, but I could not find places to reduce the complexity
without removing scenarios that seem reasonably likely to pop-up in real-world
transitions.
--Paul Hoffman
On Oct 20, 2011, at 10:50 AM, Sandra Murphy wrote:
The authors have requested a WG LC for draft Algorithm Agility Procedure for
RPKI.
The document and the draft version history are available at
http://tools.ietf.org/html/draft-ietf-sidr-algorithm-agility-03
The last call will end Thu,
Some comments.
Section 4.3. Phase 0
I'm still struggling to see the necessity to put in the operational dates
for a Alg shift in [I-D.ietf-sidr-rpki-algs]. I concur that the future Alg
suite and to be EOL's suite should be identified once suitable candidates
have been selected in rpki-algs. But
Hi Randy,
On Oct 30, 2011, at 4:57 AM, Randy Bush wrote:
[--snip--]
1) From Section 3:
---snip---
A local valid cache containing all RPKI data may be gathered from the
global distributed database using the rsync protocol, [RFC5781], and
a validation tool such as rcynic [rcynic].
