Re: [sidr] Current document status && directionz

[Randy Bush]

> yes, the chairs posed the question: "Err, did we sink your battleship
> with too many docks?" to alvaro, he's still using his snorkel to swim
> out of the trench... he'll get there he says :)

it would seem desirable to get them through the iesg before closing sidr
and transitioning to sidrops.

randy

___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr

Re: [sidr] Current document status && directionz

[Christopher Morrow]

On Wed, Oct 26, 2016 at 11:18 PM, Randy Bush  wrote:

> > Currently we have the following in IESG/pub-request status (13
> documents):
> > draft-ietf-sidr-adverse-actions
> > draft-ietf-sidr-as-migration
> > draft-ietf-sidr-bgpsec-algs
> > draft-ietf-sidr-bgpsec-ops
> > draft-ietf-sidr-bgpsec-overview
> > draft-ietf-sidr-bgpsec-pki-profiles
> > draft-ietf-sidr-bgpsec-protocol
> > draft-ietf-sidr-origin-validation-signaling
> > draft-ietf-sidr-publication
> > draft-ietf-sidr-rpki-oob-setup
> > draft-ietf-sidr-rpki-rtr-rfc6810-bis
> > draft-ietf-sidr-delta-protocol (10/26 sent forward)
> > draft-ietf-sidr-rpki-validation-reconsidered (10/26 sent forward)
>
> an interesting view on progress of these documents is visible in
> https://datatracker.ietf.org/doc/ad/alvaro.retana/


yes, the chairs posed the question: "Err, did we sink your battleship with
too many docks?" to alvaro, he's still using his snorkel to swim out of the
trench... he'll get there  he says :)

(and basically we did our job pushing documents forward and working through
the discussions 'we' here == 'working-group' not 'me'  Thanks to the WG
folk for doing some hard work and focusing)

-chris
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr

Re: [sidr] Current document status && directionz

[Randy Bush]

> Currently we have the following in IESG/pub-request status (13 documents):
> draft-ietf-sidr-adverse-actions
> draft-ietf-sidr-as-migration
> draft-ietf-sidr-bgpsec-algs
> draft-ietf-sidr-bgpsec-ops
> draft-ietf-sidr-bgpsec-overview
> draft-ietf-sidr-bgpsec-pki-profiles
> draft-ietf-sidr-bgpsec-protocol
> draft-ietf-sidr-origin-validation-signaling
> draft-ietf-sidr-publication
> draft-ietf-sidr-rpki-oob-setup
> draft-ietf-sidr-rpki-rtr-rfc6810-bis
> draft-ietf-sidr-delta-protocol (10/26 sent forward)
> draft-ietf-sidr-rpki-validation-reconsidered (10/26 sent forward)

an interesting view on progress of these documents is visible in
https://datatracker.ietf.org/doc/ad/alvaro.retana/

randy

___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr

Re: [sidr] Current document status && directionz

[Christopher Morrow]

Restarting this thread, with some updates :)

Preparing for Seoul in a few weeks time, with the intent that we do not
meet face-to-face in Chicago, have all current 'protocol' related docs to
the IESG/done and meet instead in sidr-ops if there are agenda items at
that time :)

Currently we have the following in IESG/pub-request status (13 documents):
draft-ietf-sidr-adverse-actions
draft-ietf-sidr-as-migration
draft-ietf-sidr-bgpsec-algs
draft-ietf-sidr-bgpsec-ops
draft-ietf-sidr-bgpsec-overview
draft-ietf-sidr-bgpsec-pki-profiles
draft-ietf-sidr-bgpsec-protocol
draft-ietf-sidr-origin-validation-signaling
draft-ietf-sidr-publication
draft-ietf-sidr-rpki-oob-setup
draft-ietf-sidr-rpki-rtr-rfc6810-bis
draft-ietf-sidr-delta-protocol (10/26 sent forward)
draft-ietf-sidr-rpki-validation-reconsidered (10/26 sent forward)


Currently still active documents (8 documents):
draft-ietf-sidr-bgpsec-rollover
draft-ietf-sidr-lta-use-cases
draft-ietf-sidr-route-server-rpki-light
draft-ietf-sidr-rpki-tree-validation
draft-ietf-sidr-rpki-validation-reconsidered
draft-ietf-sidr-rtr-keying
draft-ietf-sidr-slurm

(this reflects the changes since the last email, included below)

I believe we're still planning to move (and have agreement from authors):
 draft-ietf-sidr-bgpsec-rollover
 draft-ietf-sidr-lta-use-cases
 draft-ietf-sidr-route-server-rpki-light
 draft-ietf-sidr-rtr-keying

which leaves to be dealt with by Chicago 2 documents:
draft-ietf-sidr-rpki-tree-validation
draft-ietf-sidr-slurm

I think this is good, I believe (and of course I should be corrected if
wrong)
  slurm - more work inbound and discussion planned in Seoul
  tree-validation - I thought moved to sidr-ops, but don't have docs to
back that up.

-chris

On Fri, Sep 2, 2016 at 4:56 PM, Chris Morrow  wrote:

>
> Howdy SIDR peeps,
> (+bonus ops ad)
>
> Following on the Berlin meeting we were trying to accomplish two
> things:
>
>   1) get all documents related to sidr protocols into wglc and then
>   publication
>
>   2) get all documents which are more operationally focused moved
>   along to an ops group (sidr-ops or something akin to that)
>
> With that in mind there are 8 documents in the publication queue:
>   draft-ietf-sidr-as-migration
>   draft-ietf-sidr-bgpsec-algs
>   draft-ietf-sidr-bgpsec-ops
>   draft-ietf-sidr-bgpsec-overview
>   draft-ietf-sidr-bgpsec-pki-profiles
>   draft-ietf-sidr-bgpsec-protocol
>   draft-ietf-sidr-origin-validation-signaling
>   draft-ietf-sidr-rpki-rtr-rfc6810-bis
>
> and 11 still in progress. Of the 11 left Sandy and I think they
> roughly break down like:
>
> Documents which should move to the ops group:
>   draft-ietf-sidr-bgpsec-rollover
>   draft-ietf-sidr-lta-use-cases
>   draft-ietf-sidr-route-server-rpki-light - authors notified/queried
> about this
>   draft-ietf-sidr-rtr-keying
>
> documents which should finish out in sidr:
>   draft-ietf-sidr-delta-protocol
>   draft-ietf-sidr-publication
>   draft-ietf-sidr-rpki-oob-setup - pub request in flight
>   draft-ietf-sidr-rpki-tree-validation
>   draft-ietf-sidr-rpki-validation-reconsidered
>   draft-ietf-sidr-slurm - authors recently updated
>   draft-ietf-sidr-adverse-actions - wglc imminent
>
> I think if there's no meaningful discussion on change for these
> between now and 9/16/2016 (Sept 16th) we will assume this list is
> correct. For documents in the 'move' list, if progress to publication
> happens 'good!'. For all documents in the 'stays' list:
>   1) we aim to have wglc by Seoul
>   2) publication requests started on as many as possible
>
> We plan to meet in Seoul, but not in Chicago (Mar 2017) where we
> expect the ops group to exist and meet. We can progress documents in
> SIDR after Seoul, but the WG should close out shortly after the new
> year. (or that's the goal).
>
> Thoughts?
> -chris
>
> ___
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr

Re: [sidr] WGLC - draft-ietf-sidr-rpki-validation-reconsidered - ends 10/25/2016

[Christopher Morrow]

I'll prepare the shepherd doc and await an ack/nack to this mail before
pushing forward to IESG.

On Wed, Oct 26, 2016 at 11:32 AM, Tim Bruijnzeels  wrote:

> Hi Sean, Tom, Russ, and all,
>
> Sorry for bringing this up late. Technically past 25 October, and yes I
> would like to see this go through as you might expect from an author...
>
> That said, can someone with good ASN.1-fu please have look at the changes
> w.r.t. ASN.1 structure and OIDs? I tried to include all your comments
> properly - but I would feel safer if one of you could confirm.
>
> Thanks
> Tim
>
>
> > On 26 Oct 2016, at 05:13, Sriram, Kotikalapudi (Fed) <
> kotikalapudi.sri...@nist.gov> wrote:
> >
> > I read the draft once again. I support publication.
> >
> > Found a minor typo in the last paragraph on p.15 (can be dealt with
> during RFC editor review process):
> > s/the loss of on IP address prefix from the VRS-IP/the loss of one IP
> address prefix from the VRS-IP/
> >
> > Sriram
> >
> > 
> > From: sidr  on behalf of Chris Morrow <
> morr...@ops-netman.net>
> > Sent: Tuesday, October 11, 2016 10:08 AM
> > To: sidr@ietf.org; sidr-cha...@ietf.org; sidr-...@ietf.org
> > Subject: [sidr] WGLC - draft-ietf-sidr-rpki-validation-reconsidered -
> ends  10/25/2016
> >
> > Howdy WG folks!
> > The authors of:
> >  draft-ietf-sidr-rpki-validation-reconsidered
> >
> > believe they have addressed all inflight concerns/comments, the
> > request is to WGLC this, consider it's place in the world and if
> > appropriate pass this document along to the IESG for publication.
> >
> > The abstract for this draft is:
> >  "This document proposes an update to the certificate validation
> >   procedure specified in RFC 6487 that reduces aspects of operational
> >   fragility in the management of certificates in the RPKI, while
> >   retaining essential security features."
> >
> > Let's have a read through, consider and reply with your thoughts please,
> > this WGLC is set to expire: 10/25/2016 - October 25, 2016.
> >
> > thanks for reading/replying/thinking!
> > -chris
> > co-chair-persona
> >
> > ___
> > sidr mailing list
> > sidr@ietf.org
> > https://www.ietf.org/mailman/listinfo/sidr
>
> ___
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr

Re: [sidr] WGLC - draft-ietf-sidr-rpki-validation-reconsidered - ends 10/25/2016

[Tim Bruijnzeels]

Hi Sean, Tom, Russ, and all,

Sorry for bringing this up late. Technically past 25 October, and yes I would 
like to see this go through as you might expect from an author...

That said, can someone with good ASN.1-fu please have look at the changes 
w.r.t. ASN.1 structure and OIDs? I tried to include all your comments properly 
- but I would feel safer if one of you could confirm.

Thanks
Tim


> On 26 Oct 2016, at 05:13, Sriram, Kotikalapudi (Fed) 
>  wrote:
> 
> I read the draft once again. I support publication.
> 
> Found a minor typo in the last paragraph on p.15 (can be dealt with during 
> RFC editor review process):
> s/the loss of on IP address prefix from the VRS-IP/the loss of one IP address 
> prefix from the VRS-IP/
> 
> Sriram
> 
> 
> From: sidr  on behalf of Chris Morrow 
> 
> Sent: Tuesday, October 11, 2016 10:08 AM
> To: sidr@ietf.org; sidr-cha...@ietf.org; sidr-...@ietf.org
> Subject: [sidr] WGLC - draft-ietf-sidr-rpki-validation-reconsidered - ends
>   10/25/2016
> 
> Howdy WG folks!
> The authors of:
>  draft-ietf-sidr-rpki-validation-reconsidered
> 
> believe they have addressed all inflight concerns/comments, the
> request is to WGLC this, consider it's place in the world and if
> appropriate pass this document along to the IESG for publication.
> 
> The abstract for this draft is:
>  "This document proposes an update to the certificate validation
>   procedure specified in RFC 6487 that reduces aspects of operational
>   fragility in the management of certificates in the RPKI, while
>   retaining essential security features."
> 
> Let's have a read through, consider and reply with your thoughts please,
> this WGLC is set to expire: 10/25/2016 - October 25, 2016.
> 
> thanks for reading/replying/thinking!
> -chris
> co-chair-persona
> 
> ___
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr

___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr

Re: [sidr] WGLC - draft-ietf-sidr-rpki-validation-reconsidered - ends 10/25/2016

[Christopher Morrow]

howdy! it's past 10/25, so... I think despite seeing only 2 folk reply I
think this document should move forward, so I'll send up a pub-request
shortly.

On Tue, Oct 25, 2016 at 11:13 PM, Sriram, Kotikalapudi (Fed) <
kotikalapudi.sri...@nist.gov> wrote:

> I read the draft once again. I support publication.
>
> Found a minor typo in the last paragraph on p.15 (can be dealt with during
> RFC editor review process):
> s/the loss of on IP address prefix from the VRS-IP/the loss of one IP
> address prefix from the VRS-IP/
>
> Sriram
>
> 
> From: sidr  on behalf of Chris Morrow <
> morr...@ops-netman.net>
> Sent: Tuesday, October 11, 2016 10:08 AM
> To: sidr@ietf.org; sidr-cha...@ietf.org; sidr-...@ietf.org
> Subject: [sidr] WGLC - draft-ietf-sidr-rpki-validation-reconsidered -
> ends  10/25/2016
>
> Howdy WG folks!
> The authors of:
>   draft-ietf-sidr-rpki-validation-reconsidered
>
> believe they have addressed all inflight concerns/comments, the
> request is to WGLC this, consider it's place in the world and if
> appropriate pass this document along to the IESG for publication.
>
> The abstract for this draft is:
>   "This document proposes an update to the certificate validation
>procedure specified in RFC 6487 that reduces aspects of operational
>fragility in the management of certificates in the RPKI, while
>retaining essential security features."
>
> Let's have a read through, consider and reply with your thoughts please,
> this WGLC is set to expire: 10/25/2016 - October 25, 2016.
>
> thanks for reading/replying/thinking!
> -chris
> co-chair-persona
>
> ___
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>
> ___
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr

Re: [sidr] WGLC - draft-ietf-sidr-delta-protocol - 10/25/2016

[Christopher Morrow]

Thanks for reading (everyone) and commenting (many folks)

this is being sent forward to the IESG now.

On Fri, Oct 21, 2016 at 12:19 PM, Sean Turner  wrote:

> This whole concept is analogous to existing DAP/LDAP mechanism and the
> “delta” concept in CRLs.  Considering this protocol is run over https it
> seems like a step in the right direction away from unsecured rsync.  So the
> idea seems sensible and after re-reading the draft I think we are a go for
> launch [0].
>
> spt
>
> [0] https://www.youtube.com/watch?v=zVf-rehP4b8
>
> > On Oct 20, 2016, at 10:19, Christopher Morrow 
> wrote:
> >
> > Howdy!
> > 5 more days until this call expires, please read and comment... or at
> least say:
> >   "Hey! I did read this it is [awesome|horrible|acceptable|
> dumpsterfire]"
> >
> > thanks!
> > -chris
> > (feel free to cut/paste/edit the quote if it'll save you time)
> >
> > On Tue, Oct 11, 2016 at 10:15 AM, Chris Morrow 
> wrote:
> >
> > Howdy WG Folks!
> > Let's chat (email) about the subject document:
> >   draft-ietf-sidr-delta-protocol
> >
> > The authors believe they have dealt with all open items and are
> > interested in moving this document forward to IESG for
> > publication. Let's have a read/write/arithmetic time with the draft
> > and send comments/questions/suggestions/etc to the list for the
> > authors to handle or, possibly just: "yea! move this document along!"
> > if you believe it's ready for the next step in it's lifecycle.
> >
> > The WGLC should end 10/25/2016 - October 25th 2016.
> >
> > The abstract for this document is:
> >   "In the Resource Public Key Infrastructure (RPKI), certificate
> >authorities publish certificates, including end entity certificates,
> >Certificate Revocation Lists (CRL), and RPKI signed objects to
> >repositories.  Relying Parties (RP) retrieve the published
> >information from those repositories.  This document specifies a delta
> >protocol which provides relying parties with a mechanism to query a
> >repository for incremental updates, thus enabling the RP to keep its
> >state in sync with the repository."
> >
> > thanks!
> > -chris
> > co-chair-persona
> >
> > ___
> > sidr mailing list
> > sidr@ietf.org
> > https://www.ietf.org/mailman/listinfo/sidr
> >
> > ___
> > sidr mailing list
> > sidr@ietf.org
> > https://www.ietf.org/mailman/listinfo/sidr
>
>
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr