Re: [regext] WGLC: https://datatracker.ietf.org/doc/draft-ietf-regext-allocation-token
I believe there is either a minor omission or punctuation error at Page 17: 6.3. Neustar gTLD SRS Organisation: Neustar Inc. Gould & Feher Expires July 6, 2018 [Page 17] Internet-Draft allocationTokenJanuary 2018 Name: Neustar generic Top Level Domain (gTLD) Shared Registry System (SRS). Description: The Neustar gTLD SRS implements the server side of draft-ietf-regext-allocation-token. For several Top Level Domains Level of maturity: Production The description probably meant to be a single phrase. But it is not a show stopper for the document if the correction is to be done further down the road, since the meaning is unequivocal. Rubens > On 12 Jan 2018, at 11:32, James Galvinwrote: > > The document editors have indicated that the following document is ready for > submission to the IESG to be considered for publication as a Proposed > Standard: > > Allocation Token Extension for the Extensible Provisioning Protocol (EPP) > https://datatracker.ietf.org/doc/draft-ietf-regext-allocation-token-05 > > If any working group member objects to the publication of this document > please respond on the list by close of business everywhere, Friday, 26 > January 2018. If there are no objections the document will be submitted to > the IESG. > > During the last call the chairs are looking for a document shepherd for this > document. If you are interesting in being the document shepherd please let > the chairs know. The document editors can not be the document shepherd. > > Thanks, > > Antoin and Jim > WG Co-Chairs > > ___ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext signature.asc Description: Message signed with OpenPGP ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
Re: [regext] Call for adoption: draft-hollenbeck-regext-rdap-object-tag
Will do - thanks! Scott > -Original Message- > From: regext [mailto:regext-boun...@ietf.org] On Behalf Of Antoin > Verschuren > Sent: Friday, January 12, 2018 8:56 AM > To: Registration Protocols Extensions> Subject: [EXTERNAL] Re: [regext] Call for adoption: draft-hollenbeck- > regext-rdap-object-tag > > Dear all, > > Sorry for the delay, but since we had no objections and 2 non-authors > supporting adoption, the chairs now declare this document adopted. > Scott, if you submit a new version of the document it can be renamed and > we will put it in our milestones list and change the state accordingly. > We have set up a pre-approvel for a draft-ietf-regext-rdap-object-tag-00 > document name. > > Regards, > > Jim and Antoin > > - -- > Antoin Verschuren > > Tweevoren 6, 5672 SB Nuenen, NL > M: +31 6 37682392 > > > > > > > Op 13 dec. 2017, om 14:44 heeft Antoin Verschuren het > volgende geschreven: > > > Hi all, > > > > As discussed in Singapore, we have cleaned up our list of action items > and moved documents along to the IESG and into working group last call, so > we can now adopt new documents. > > This is a formal adoption request for draft-hollenbeck-regext-rdap- > object-tag > > > > The draft is available here: > > https://datatracker.ietf.org/doc/draft-hollenbeck-regext-rdap-object- > tag/ > > > > Please review this draft to see if you think it is suitable for adoption > by REGEXT, and comment to the list, clearly stating your view. > > Please also indicate if you are willing to contribute text, review, etc. > > > > This call for adoption ends 20 December 2017. > > If there are no objections, and we receive enough consensus for > adoption, the chairs will consider this document adopted. > > > > Thanks, > > > > Your REGEXT co-chairs Jim and Antoin. > > > > - -- > > Antoin Verschuren > > > > Tweevoren 6, 5672 SB Nuenen, NL > > M: +31 6 37682392 > > > > > > > > > > > > ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
Re: [regext] EPP and DNAME records?
On Sat, Jan 06, 2018 at 08:01:02PM +0100, Patrick Mevzekwrote a message of 77 lines which said: > * I have mixed feelings about section 10. > Specifically you state: > A trust relationship MUST exist between the EPP client and >server, and provisioning of DNAME delegation MUST only be done after >the identities of both parties have been confirmed using a strong >authentication mechanism. > > Does that mean that provisions in RFC5734 (specifically section 8) are not > enough to provide that? I don't have a strong opinion here. Should the draft be adopted, I would be happy to defer to the WG decision. In the mean time, I see no harm in repeating this. Many RFC have security considerations sections which are as surprising as "remember that water is wet and fire is hot". ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
Re: [regext] Call for adoption: draft-hollenbeck-regext-rdap-object-tag
Dear all, Sorry for the delay, but since we had no objections and 2 non-authors supporting adoption, the chairs now declare this document adopted. Scott, if you submit a new version of the document it can be renamed and we will put it in our milestones list and change the state accordingly. We have set up a pre-approvel for a draft-ietf-regext-rdap-object-tag-00 document name. Regards, Jim and Antoin - -- Antoin Verschuren Tweevoren 6, 5672 SB Nuenen, NL M: +31 6 37682392 Op 13 dec. 2017, om 14:44 heeft Antoin Verschurenhet volgende geschreven: > Hi all, > > As discussed in Singapore, we have cleaned up our list of action items and > moved documents along to the IESG and into working group last call, so we can > now adopt new documents. > This is a formal adoption request for draft-hollenbeck-regext-rdap-object-tag > > The draft is available here: > https://datatracker.ietf.org/doc/draft-hollenbeck-regext-rdap-object-tag/ > > Please review this draft to see if you think it is suitable for adoption by > REGEXT, and comment to the list, clearly stating your view. > Please also indicate if you are willing to contribute text, review, etc. > > This call for adoption ends 20 December 2017. > If there are no objections, and we receive enough consensus for adoption, the > chairs will consider this document adopted. > > Thanks, > > Your REGEXT co-chairs Jim and Antoin. > > - -- > Antoin Verschuren > > Tweevoren 6, 5672 SB Nuenen, NL > M: +31 6 37682392 > > > > > > signature.asc Description: Message signed with OpenPGP using GPGMail ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
[regext] WGLC: https://datatracker.ietf.org/doc/draft-ietf-regext-allocation-token
The document editors have indicated that the following document is ready for submission to the IESG to be considered for publication as a Proposed Standard: Allocation Token Extension for the Extensible Provisioning Protocol (EPP) https://datatracker.ietf.org/doc/draft-ietf-regext-allocation-token-05 If any working group member objects to the publication of this document please respond on the list by close of business everywhere, Friday, 26 January 2018. If there are no objections the document will be submitted to the IESG. During the last call the chairs are looking for a document shepherd for this document. If you are interesting in being the document shepherd please let the chairs know. The document editors can not be the document shepherd. Thanks, Antoin and Jim WG Co-Chairs ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
[regext] WGLC: https://datatracker.ietf.org/doc/draft-ietf-regext-change-poll
The document editors have indicated that the following document is ready for submission to the IESG to be considered for publication as a Proposed Standard: Change Poll Extension for the Extensible Provisioning Protocol (EPP) https://datatracker.ietf.org/doc/draft-ietf-regext-change-poll-06 If any working group member objects to the publication of this document please respond on the list by close of business everywhere, Friday, 26 January 2018. If there are no objections the document will be submitted to the IESG. During the last call the chairs are looking for a document shepherd for this document. If you are interesting in being the document shepherd please let the chairs know. The document editors can not be the document shepherd. Thanks, Antoin and Jim WG Co-Chairs ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext