[sidr] Terry Manderson's No Objection on draft-ietf-sidr-delta-protocol-07: (with COMMENT)

Terry Manderson has entered the following ballot position for draft-ietf-sidr-delta-protocol-07: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please ref

Re: [sidr] Terry Manderson's No Objection on draft-ietf-sidr-delta-protocol-07: (with COMMENT)

Hi Terry, all, > On 16 Feb 2017, at 03:03, Terry Manderson wrote: > > Terry Manderson has entered the following ballot position for > draft-ietf-sidr-delta-protocol-07: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To a

Re: [sidr] Terry Manderson's No Objection on draft-ietf-sidr-delta-protocol-07: (with COMMENT)

Hi! I just want to provide a little bit more background on the topic below – and ask the Chairs to take an action to confirm with the WG. During the discussion resulting from my AD review of this document [1], the topic of whether the intent of the document was to replace rsync or not came up

Re: [sidr] Terry Manderson's No Objection on draft-ietf-sidr-delta-protocol-07: (with COMMENT)

lvaro Retana (aretana) Sent: Friday, February 17, 2017 9:56:41 AM To: Tim Bruijnzeels; Terry Manderson; sidr-cha...@ietf.org; morr...@ops-netman.net; sa...@tislabs.com Cc: draft-ietf-sidr-delta-proto...@ietf.org; The IESG; sidr@ietf.org Subject: Re: [sidr] Terry Manderson's No Objection on draft

Re: [sidr] Terry Manderson's No Objection on draft-ietf-sidr-delta-protocol-07: (with COMMENT)

> As Terry mentions below, these changes removed “the quality of a > mandatory to implement retrieval mechanism”: rsync is no longer > mandatory to implement, but neither is RRDP. this is gonna work out really well for distributed clients and distributed servers where every client must to talk to

Re: [sidr] Terry Manderson's No Objection on draft-ietf-sidr-delta-protocol-07: (with COMMENT)

9:56:41 AM > To: Tim Bruijnzeels; Terry Manderson; sidr-cha...@ietf.org; > morr...@ops-netman.net; sa...@tislabs.com > Cc: draft-ietf-sidr-delta-proto...@ietf.org; The IESG; sidr@ietf.org > Subject: Re: [sidr] Terry Manderson's No Objection on > draft-ietf-sidr-delta-protocol-07: (

Re: [sidr] Terry Manderson's No Objection on draft-ietf-sidr-delta-protocol-07: (with COMMENT)

FWIW, I would prefer to leave rsync's status alone for now (i.e. still mandatory) and handle the transition later via separate docs, probably in SIDROPS, per the original plan. -- Sent from a phone, please excuse brevity and typos.___ sidr mailing list

Re: [sidr] Terry Manderson's No Objection on draft-ietf-sidr-delta-protocol-07: (with COMMENT)

Tim: Hi! Given the feedback so far on the list, I think we should roll back the updates in preparation for next week’s IESG Telechat. Thanks! Alvaro. On 2/17/17, 9:56 AM, "sidr on behalf of Alvaro Retana (aretana)" mailto:sidr-boun...@ietf.org> on behalf of aret...@cisco.com

Re: [sidr] Terry Manderson's No Objection on draft-ietf-sidr-delta-protocol-07: (with COMMENT)

Hi everybody, > On 23 Feb 2017, at 20:25, Alvaro Retana (aretana) wrote: > > Tim: > > Hi! > > Given the feedback so far on the list, I think we should roll back the > updates in preparation for next week’s IESG Telechat. Currently RFC7730 (TAL format) only allows rsync URIs in there. In o

Re: [sidr] Terry Manderson's No Objection on draft-ietf-sidr-delta-protocol-07: (with COMMENT)

Hi all, > On 27 Feb 2017, at 10:24, Oleg Muravskiy wrote: > > Hi everybody, > >> On 23 Feb 2017, at 20:25, Alvaro Retana (aretana) wrote: >> >> Tim: >> >> Hi! >> >> Given the feedback so far on the list, I think we should roll back the >> updates in preparation for next week’s IESG Telecha

Re: [sidr] Terry Manderson's No Objection on draft-ietf-sidr-delta-protocol-07: (with COMMENT)

[Late response] At Tue, 28 Feb 2017 15:25:49 +0100, Tim Bruijnzeels wrote: > > On 27 Feb 2017, at 10:24, Oleg Muravskiy wrote: ... > > In order to allow RRDP in TAL, I think we have to keep the update > > to RFC7730 in draft-ietf-sidr-delta-protocol, namely this part of > > the draft: > > While