Sandy,
I can’t parse “but using the constraints applied come from this specification”.
Can you clarify?
The text I supplied for the replacement validation alg were based on the
original text, whenever possible. Unfortunately, the original text
refers to sections of 6487 implicitly as "this
Speaking as regular ol’ member:
> On Jul 15, 2016, at 1:28 PM, Stephen Kent wrote:
>
> Tim,
>
> I reviewed the -06 version and am attaching a pdf of the MS Word file with
> suggested edits. I can send you the word file itself if you wish.
>
> I have provided text to my
> On Jul 08, 2016, at 09:00, Sean Turner wrote:
>
>
>> On Jul 08, 2016, at 05:35, Tim Bruijnzeels wrote:
>>
>> Stephen Kent comment on -04 of this document saying that it should not
>> attempt to update the BGPSec Router Certificate I-D because it's not an
> On Jul 08, 2016, at 05:35, Tim Bruijnzeels wrote:
>
> Stephen Kent comment on -04 of this document saying that it should not
> attempt to update the BGPSec Router Certificate I-D because it's not an RFC,
> just yet. It's currently in IESG Processing. The current document
Dear WG,
After receiving some feedback on the previous version and discussion with
co-authors, this version:
- Does not reject 'over-claiming' EE certificates, but uses VRS-IP/AS there as
well
- Includes text to update ROA validation (in short requires that all prefixes
are in VRS-IP of the
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 of the IETF.
Title : RPKI Validation Reconsidered
Authors : Geoff Huston
George Michaelson