Re: [sidr] ORIGINs

2013-03-12 Thread Stephen Kent
Danny, On 2013-03-11 13:31, Stephen Kent wrote: Danny, We have been told by several operators that the values stated in Section 4.3 of RFC 4271 are not what is used today. We also have been told that, contrary to the SHOULD NOT in Section 5.1.1 of this RFC, it is not uncommon for ASes to

Re: [sidr] ORIGINs

2013-03-12 Thread Danny McPherson
On 2013-03-12 07:07, Stephen Kent wrote: As far as I'm concerned, we're going to follow IETF procedures. That charter was intentionally worded when it was written so that the solution envisaged would be the only thing worked on here, absent being information by any actual threats or

Re: [sidr] ORIGINs

2013-03-12 Thread Matthew Lepinski
A quick clarification: The current BGPSEC protocol specification can easily be modified to protect the ORIGIN attribute. (That is, prevent it from being modified by intermediate ASes.) I can very quickly put out an update to the BGPSEC protocol specification if the working group decides that

Re: [sidr] ORIGINs

2013-03-12 Thread Christopher Morrow
On Tue, Mar 12, 2013 at 9:38 AM, Matthew Lepinski mlepinski.i...@gmail.com wrote: A quick clarification: The current BGPSEC protocol specification can easily be modified to protect the ORIGIN attribute. (That is, prevent it from being modified by intermediate ASes.) I can very quickly put out

Re: [sidr] ORIGINs

2013-03-12 Thread Randy Bush
A quick clarification: The current BGPSEC protocol specification can easily be modified to protect the ORIGIN attribute. (That is, prevent it from being modified by intermediate ASes.) ops with deep clue and who i respct have spoken. don't do it. randy

Re: [sidr] Fwd: New Version Notification for draft-rogaglia-sidr-multiple-publication-points-02.txt

2013-03-12 Thread Andy Newton
On 3/11/13 9:59 AM, Carlos M. Martinez carlosm3...@gmail.com wrote: As requested by the chairs, I'm sending this email requesting WG adoption of this item. I support the adoption of this draft as a working group item. -andy ___ sidr mailing list

[sidr] wg adoption call for draft-rogaglia-sidr-multiple-publication-points

2013-03-12 Thread Murphy, Sandra
The authors of draft-rogaglia-sidr-multiple-publication-points have requested wg adoption. See http://tools.ietf.org/html/draft-rogaglia-sidr-multiple-publication-points Please do respond to the list as to whether you support the wg adopting this as a work item. Note that you do not need to

Re: [sidr] ORIGINs

2013-03-12 Thread Jon Mitchell
On 12/03/13 10:21 -0400, Christopher Morrow wrote: On Tue, Mar 12, 2013 at 9:38 AM, Matthew Lepinski mlepinski.i...@gmail.com wrote: A quick clarification: The current BGPSEC protocol specification can easily be modified to protect the ORIGIN attribute. (That is, prevent it from being

Re: [sidr] wg adoption call for draft-rogaglia-sidr-multiple-publication-points

2013-03-12 Thread Di Ma
I support adoption of this document, the discussion of which is going to make a better RPKI deployment. Di Ma China Internet Network Information Center (CNNIC) 在 2013-3-12,下午1:54,Murphy, Sandra sandra.mur...@sparta.com 写道: The authors of draft-rogaglia-sidr-multiple-publication-points have

Re: [sidr] wg adoption call for draft-rogaglia-sidr-multiple-publication-points

2013-03-12 Thread Arturo Servin
Support and willing to review and comment. .as On 12/03/2013 13:54, Murphy, Sandra wrote: The authors of draft-rogaglia-sidr-multiple-publication-points have requested wg adoption. See http://tools.ietf.org/html/draft-rogaglia-sidr-multiple-publication-points Please do