At Mon, 5 Sep 2016 19:54:53 -0300, "Carlos M. Martinez" <[email protected]> wrote: > > Here is the pointer to the document: > > https://tools.ietf.org/html/draft-rir-rpki-allres-ta-app-statement-01 > > Apologies for my earlier laziness.
no worries, yes Sandy and I chatted about this... err, I think the end result was: "is this an ops thing? should this go to ops? or should we just adopt it in SIDR and jam it through?" I think sandy was due to send 'authors'(you/andy/etc) a mail about this... oh and we're waiting on Alvaro to reply to this as well. I'll mail an update to the list. > > On 9/5/2016 3:32 PM, Carlos M. Martinez wrote: > > Hi Chris, > > > > I know we already discussed this over private email, but perhaps you can > > comment on the list on the future of the requested WG adoption call for > > the ‘all resources’ applicability statement draft. > > > > thanks! > > > > -Carlos > > > > On 2 Sep 2016, at 17:56, 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 > >> [email protected] > >> https://www.ietf.org/mailman/listinfo/sidr _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
