Hi all,
Sorry for not responding to this earlier, but after an extended vacation it
took me quite some time to digest the discussion and form an opinion.
We would like you to know that I have published the agenda for IETF114, and we
have reserved a 30 minutes discussion on this topic.
We would
Hi All,
Ii’s time to think about agenda items for IETF 115 to see how much time we need
for our meeting.
Jim and I are thinking to request a same one hour time slot as last IETF 114
meeting, unless we get a lot of requests from you for new work.
So if you intend to request for a presentation,
Dear Working Group,
The authors of the following working group document have indicated that it is
believed to be ready for submission to the IESG for publication as a standards
track document:
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-reverse-search/
This WG last call will end at
support (a simple “+1” is sufficient) or
concerns with the publication of this document by replying to this message on
the list.
Regards,
Jim and Antoin
> Op 12 sep. 2022, om 15:54 heeft Antoin Verschuren
> het volgende geschreven:
>
> Dear Working Group,
>
> The author
m and Antoin
> Op 26 sep. 2022, om 11:46 heeft Mario Loffredo
> het volgende geschreven:
>
> Hi Patrick,
>
> thanks for your review.
>
> Please find my comments inline.
>
> Il 25/09/2022 18:21, Patrick Mevzek ha scritto:
>> On Mon, Sep 12, 2022, at 08:54, A
make this statement?
After all these are addressed, then we can declare consensus and move the
document along.
> Op 26 sep. 2022, om 16:00 heeft Antoin Verschuren
> het volgende geschreven:
>
> Given the discussion below, we are considering to extend this WGLC for at
> mo
material change, we will issue another WGLC once the document is stable and all
issues are addressed, so that we can make a clear consensus call on the final
stable version of this document.
Regards,
Jim and Antoin
> Op 3 okt. 2022, om 15:26 heeft Antoin Verschuren
> het volgende gesc
Hi all, can all people that commented on draft-ietf-regext-rdap-reverse-search
since the start of the previous last call (Tom, Pawel, Jasdip) confirm that all
their issues are now addressed in version 17, so that the document shepherd can
confirm there are no new changes to be expected during WG
This is the formal adoption request for RDAP RIR Search:
https://datatracker.ietf.org/doc/draft-harrison-regext-rdap-rir-search/
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.
This Call For Adoption
00 is published.
Thanks,
Jim and Antoin
> Op 19 dec. 2022, om 15:33 heeft Antoin Verschuren
> het volgende geschreven:
>
> This is the formal adoption request for RDAP RIR Search:
>
> https://datatracker.ietf.org/doc/draft-harrison-regext-rdap-rir-search/
>
>
Hi All,
Ii’s time to think about agenda items for IETF 116.
Jim and I requested an hour time slot, same as last IETF 115 meeting.
So if you intend to request for a presentation, please let the chairs know.
Regards,
Jim and Antoin
___
regext mailing
gt; --Dan
>
> On 2/13/23, 9:18 AM, "regext on behalf of Antoin Verschuren"
> mailto:regext-boun...@ietf.org> on behalf of
> ietf=40antoin...@dmarc.ietf.org <mailto:40antoin...@dmarc.ietf.org>> wrote:
>
>
> Caution: This email originated from outsi
Tom,
Since you were the last one to comment, can you please confirm that the issues
you raised on version 17 of this document are now resolved and the document is
stable so we can issue a WGLC?
Regards,
Jim and Antoin
> Op 6 mrt. 2023, om 11:54 heeft Mario Loffredo het
> volgende geschreve
Chair hat off.
Thank you Tom for this document and your presentation. I like it a lot.
I have read this draft, and have some comments/requests as discussed during our
IETF 116 meeting session.
Most of my remarks are about section 4, Link Relations:
1. Suggest to replace “operator” with “server
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:
Redacted Fields in the Registration Data Access Protocol (RDAP) Response
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-redacted/1
This is a formal adoption request for Extensible Provisioning Protocol (EPP)
mapping for DNS Time-To-Live (TTL) values:
https://datatracker.ietf.org/doc/draft-regext-brown-epp-ttl/
Please review this draft to see if you think it is suitable for adoption by
REGEXT and comment to this mes
Mar 30, 2023 at 10:37:54AM +0200, Antoin Verschuren wrote:
>> I have read this draft, and have some comments/requests as discussed
>> during our IETF 116 meeting session.
>> Most of my remarks are about section 4, Link Relations:
>>
>> 1. Suggest to replace “operato
draft name:
draft-ietf-regext-epp-ttl
The document authors must also identify a document shepherd. If you would like
to volunteer please let them know.
Work can begin as soon as the 00 is published.
Thanks,
Jim and Antoin
> Op 25 apr. 2023, om 22:54 heeft Antoin Verschuren
> het vo
working group, and issue another WGLC when the issues are resolved.
Regards,
Jim and Antoin.
> Op 17 apr. 2023, om 15:27 heeft Antoin Verschuren
> het volgende geschreven:
>
> The document editors have indicated that the following document is ready for
> submission to the IESG t
Hi All,
Ii’s time to think about agenda items for IETF 117.
Jim and I requested a one and half hour time slot this time. Half an hour more
than IETF 116.
So if you intend to request for a presentation, please let the chairs know.
Regards,
Jim and Antoin
___
Hi All,
Ii’s time to think about agenda items for IETF 118.
Jim and I requested a one and half hour time slot this time, same as IETF 117.
So if you intend to request for a presentation, please let the chairs know.
Regards,
Jim and Antoin
___
regext
Hi Maarten,
Unfortunately, our agenda for IETF 118 is already fully booked with no space to
overrun.
Perhaps we should consider a 2 hour meeting request for next IETF 119.
Regards,
Antoin
> Op 16 okt. 2023, om 17:52 heeft Maarten Wullink
> het volgende geschreven:
>
> Hi Antoin,
>
> Maybe
t;>> Antoin,
>>>
>>> I'm willing to give up agenda items 6.iv. (rdap-extensions) and 6.v.
>>> (rdap-x-media-type) to give Maarten 10 minutes to discuss restful EPP.
>>> To me that seems like a better use of face-to-face time as both of my
>>
This is a formal adoption request for An RDAP Extension for Geofeed Data:
https://datatracker.ietf.org/doc/draft-jasdips-regext-rdap-geofeed/
Please review this draft to see if you think it is suitable for adoption by
REGEXT and comment to this message on the list, clearly stating your v
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:
RDAP RIR Search
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-rir-search/05/
Please indicate your support or no objection for t
.
Thanks,
Jim and Antoin
> Op 20 nov. 2023, om 15:36 heeft Antoin Verschuren
> het volgende geschreven:
>
> This is a formal adoption request for An RDAP Extension for Geofeed Data:
>
> https://datatracker.ietf.org/doc/draft-jasdips-regext-rdap-geofeed/
>
> Ple
Reminder,
This WGLC will end tonight. So far we only had 3 notifications of support. (And
a comment from the document shepherd)
Please indicate your support if you didn’t already do so for us to judge
consensus.
Regards,
Your co-chairs Jim and Antoin
> Op 27 nov. 2023, om 15:51 heeft Ant
Hi all,
It is time to schedule our session for IETF 119 next week.
Since we had too little time scheduled for IETF 118 where we filled our
complete 1,5 hour time slot, we are thinking of requesting 2 hours this time if
people come up with enough agenda items.
We see enough reasons on the list th
This is the formal adoption request for Best Practices for Deletion of Domain
and Host Objects in the Extensible Provisioning Protocol (EPP):
https://datatracker.ietf.org/doc/draft-hollenbeck-regext-epp-delete-bcp/
Please review this draft to see if you think it is suitable for adoption
are addressed, please write the document
shepherd writeup.
Thanks to everyone that contributed to this review!
Regards,
Jim and Antoin
REGEXT WG Co-Chairs
> Op 27 nov. 2023, om 15:51 heeft Antoin Verschuren
> het volgende geschreven:
>
> The document editors have indica
the purposes
> of signalling, and it's fine for this sort of thing to override the
> requirement above. (nro_rdap_profile_asn_flat_0 and
> nro_rdap_profile_asn_hierarchical_0 are examples of this, where the document
> itself requires implementations to pick one or the other,
chairs know.
Thanks,
Your co-chairs Jim and Antoin
> Op 29 jan. 2024, om 16:17 heeft Antoin Verschuren
> het volgende geschreven:
>
> This is the formal adoption request for Best Practices for Deletion of Domain
> and Host Objects in the Extensible Provisionin
Hi all,
I just uploaded our preliminary agenda for IETF 119 to the datatracker:
https://datatracker.ietf.org/meeting/119/materials/agenda-119-regext-00
Please verify that I didn’t forget or misinterpreted any requests and let the
chairs know if you still want a slot on our agenda.
Though our ag
can,
Regards,
- --
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
policy.
Also thinking ahead of the possibility to administer 3th party dns-operators
with limited rights agreed upon by the parent registrar, which might encounter
the same question..
Just a thought.
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 15 aug. 2016, om
and reporting, and
others don’t. Should we provision for both, or only one use case?
Thoughts?
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
signature.asc
Description: Message signed with OpenPGP using GPGMail
_
things like a demo, hacking
session, compliance testing, or a reviewers meeting request you would like to
clarify during the meeting.
Please let us know before Friday, as that is our deadline for meeting sessions
requests.
regards,
Jim and Antoin
- --
Antoin Verschuren
Tweevoren 6, 5672 SB
updates or
discussions, please do! and let us know.
Registration Protocols Extensions (REGEXT)
IETF 97, Seoul, South Korea, Agenda
Co-chairs: Jim Galvin, Antoin Verschuren
Mailinglist: regext@ietf.org
1. Welcome and Introductions (5 minutes)
i. Jabber scribe
ii. Notes scribe
iii
your opinion
on this mailinglist so Jim can summarize them in a response to the IESG.
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 9 nov. 2016, om 14:41 heeft Job Snijders het volgende
geschreven:
> On Wed, Nov 09, 2016 at 12:19:44PM +, Hollenbeck
for the
reseller object, as I think that may change the current text quite a bit..
Regards,
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 7 dec. 2016, om 09:35 heeft Linlin Zhou het volgende
geschreven:
> This is a very minor update, mostly just to
(generic role object for roles like
resellers/dns-operators/etc.).
Is there any progress or suggestion from the authors on this?
Do we need to make another call on the mailing list to get a clearer consensus
or discussion?
Do the authors want to do this themselves, or do they need any
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
the choice more difficult by inventing an option 3.
Regards,
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 18 jan. 2017, om 06:40 heeft Linlin Zhou het volgende
geschreven:
> Dear Antoin,
> Thanks for your review. Please see my feedback below.
>
afterwards to restore, or even failure of or
criticism on our industry diversity.
Regards,
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 12 jan. 2017, om 19:36 heeft Hollenbeck, Scott
het volgende geschreven:
> Is anyone interested in reviewing a pair of dra
Hi Scott,
I’ll have a preliminary agenda and call for agenda items tomorrow, just waiting
for some private responses about the working session.
Stay tuned.
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 1 mrt. 2017, om 19:57 heeft Hollenbeck, Scott het
s for our regular meeting
session will follow later today.
Regards,
Antoin and Jim.
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
regext mailing
98, Chicago, USA, Agenda
Co-chairs: Jim Galvin, Antoin Verschuren
Mailinglist: regext@ietf.org
1. Welcome and Introductions (5 minutes)
i. Jabber scribe
ii. Notes scribe
iii. NOTE WELL
2. Existing Document Status
2.a. Published (2 minutes)
i. Extensible Provisioning
.
Using a more generic "organization” object, not tagging an organization as
a one and only role as a reseller will allow an entity to have multiple roles.
This will decrease data to be maintained by both registry and the
organizations involved.
- --
Antoin Verschuren
Tweevoren 6, 56
le in relation to
a provisioning object, so they can use the new service belonging with that role.
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 3 mrt. 2017, om 16:12 heeft Gould, James het volgende
geschreven:
> I believe that “Option 1: A dedicated reseller ob
discussion that will be
published later today.
I’m happy to clarify my personal thoughts on these documents and take part in
the discussion remotely.
We will have one meetecho setup in the room, and Jim and I will schedule the
work session as to accommodate the remote participation for this dis
have enough time.
Regards,
Antoin and Jim
- --
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/ma
presenters on the agenda to please send us your
presentations so we can upload them to the datatracker for attendees to prepare.
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 24 mrt. 2017, om 22:20 heeft James Galvin het volgende
geschreven:
> Good catch!
>
Hi Andy,
I don’t have any issues with that, and I think Scott will agree, so I have
swapped those items in our new agenda for this session:
https://www.ietf.org/proceedings/98/agenda/agenda-98-regext-10
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 26 mrt
nsensus
on the mailinglist after IETF97 that this would be the path forward, and the
authors have rewritten their documents that are now eligible to be on our
milestone list. So the reseller documents will be deleted from the milestones,
but the organization documents will replace them.
- --
An
always add
them again later. But at least we will know what we are working on now, and we
could adopt new documents that do have traction.
We’re interested on your thoughts.
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 19 mei 2017, om 17:01 heeft Roger D Carney
the document was ready for WGLC to set a date in our
milestones.
The document is already adopted by the WG, but it could do with more review and
implementation experience beyond Verisign according to the authors.
regards,
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
now.
For all the other documents, we will adjust the dates as discussed.
Thank you all for your support in this discussion,
Jim and Antoin.
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 19 mei 2017, om 15:40 heeft James Galvin het volgende
geschreven
e will start the formal adoption request for this document on the
mailinglist as soon as that’s done.
Since the launchphase document shepherd finished his writeup today, there are
only some nits left for the authors to fix, so I expect this to be this/next
week.
- --
Antoin Verschuren
Tweev
reads more like a problem statement with it’s proposed processes
to solve issues of inconvenience rather than a document that defines a BCP or
makes definitions.
I’d say there is still work to do, and I can probably help with some
definitions, but let’s first start the discussion on what
this is a request to send your agenda items.
Please send in items before next friday 30 June when we will post our
preliminary agenda.
Regards,
Jim and Antoin
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
signature.asc
Description: Message signed with OpenPGP
ssion?
Regards,
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 24 jun. 2017, om 18:05 heeft Roger D Carney het
volgende geschreven:
> Good Afternoon,
>
> The latest revision, 05, of the fee draft was just posted.
>
> I would like to invite ev
soon as possible.
Another possibility is that we can still use our second (or first) hour for a
work session.
Is there any interest from document authors for this?
Regards,
Jim and Antoin
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 23 jun. 2017, om 15:41 heeft
eric phase discovery like the suggestion for a
Registry Mapping document.
We expect that this will be discussed during the interim meeting next
wednsesday.
Please comment if any of my conclusions on the consensus is incorrect.
Regards,
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, N
with one longer joint working/update session.
Thanx,
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
with one longer joint working/update session.
Thanx,
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
the desire to have a seperate working session.
We will probably opt for one longer update session where the additional time
will be dedicated to working items.
Any thoughts? Any more agenda items?
Jim and Antoin
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op
working session.
Please let us know what you think would be best.
-If there are any more agenda items, please let us know.
Registration Protocols Extensions (REGEXT)
IETF 100, Singapore, Agenda
Co-chairs: Jim Galvin, Antoin Verschuren
Mailinglist: regext@ietf.org
Update session, first hour
, Antoin Verschuren
Mailinglist: regext@ietf.org
Update session, first hour:
1. Welcome and Introductions (5 minutes)
i. Jabber scribe
ii. Notes scribe
iii. NOTE WELL
2. Existing Document Status
i. Publication requested, status (1 minute)
https://datatracker.ietf.org/doc/draft
Protocols Extensions (REGEXT)
IETF 100, Singapore, Meeting minutes
Co-chairs: Jim Galvin, Antoin Verschuren
Mailinglist: regext@ietf.org
Existing Documents
--
Launch Phase is in publication requested - all good so far.
Fee Extension (Roger Carney
Protocols Extensions (REGEXT)
IETF 100, Singapore, Meeting minutes
Co-chairs: Jim Galvin, Antoin Verschuren
Mailinglist: regext@ietf.org
Existing Documents
--
Launch Phase is in publication requested - all good so far.
Fee Extension (Roger Carney
James,
Jim and I were going to send out a formal WGLC on this document, but we didn’t
see a reply to this extensive review yet.
What do you want us to do, wait for you to have treated Patrick’s comments, or
consider them as part of WLC (Which may have a deadline)?
Jim and Antoin
- --
Antoin
Antoin
- --
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 23 nov. 2017, om 06:42 heeft Patrick Mevzek het volgende
geschreven:
> Hello James and Kal,
>
> Here are my comments on the draft:
>
> The abstract is almost longer than the introd
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
didn’t miss anything, we will make an
additional WGLC.
Since it’s holiday season, this WGLC will end January 5th.
Please review the changes made to the document, and let us know before January
5th if you have any comments.
Regards,
Jim and Antoin
- --
Antoin Verschuren
Tweevoren 6, 5672 SB
, did you get any feedback on attendance?
Regards,
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 13 dec. 2017, om 14:46 heeft James Galvin het volgende
geschreven:
> I will attend.
>
> Jim
>
>
>
> On 7 Dec 2017, at 11:36, Roger D Ca
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
session.
Should this not be enough we can also request the ad-hoc conference room for an
additional work session.
Please start thinking about agenda items and let us know what you think before
next friday when scheduling is due.
regards,
Jim and Antoin
- --
Antoin Verschuren
Tweevoren 6
week, after which we will push
harder ;-).
Regards,
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
:
Registration Protocols Extensions (REGEXT)
IETF 101, London, UK, Agenda
Co-chairs: Jim Galvin, Antoin Verschuren
Mailinglist: regext@ietf.org
*
Session I, Work session.
Monday 2018-03-19 17:40 - 18:40
Introduce the Registry Mapping concepts (Roger Carney
, be sure to voice your support during WGLC, and
volunteer to be the document shepherd ;-).
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
> kr.
>
> Pieter
>
>> On 05 Jan 2018, at 03:47, Linlin Zhou wrote:
>>
>> Dear Pierter,
>>
rest of our meeting to these topics if someone is
willing to lead them.
So please let us know if you have any agenda items.
Jim and Antoin.
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
___
regext mailing list
regext
and would show it, but a create or update could never
set it?) Or is this local policy and do we need to give guidance to registries
as to why, when and how to set this in a BCP?
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 24 mei 2018, om 15:30 heeft Gou
>
>
> James Gould
> Distinguished Engineer
> jgo...@verisign.com
>
> 703-948-3271
> 12061 Bluemont Way
> Reston, VA 20190
>
> Verisign.com <http://verisigninc.com/>
>
> On 5/25/18, 9:45 AM, "regext on behalf of Antoin Verschuren"
&
Registrant Contact Information: i...@ietf.org
The justification being that I’ve seen that term used more in wishful
presentations than privacyproxy.
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 25 mei 2018, om 20:27 heeft Gould, James
het volgende geschreven
not make things more orderly, and I could end up with a
number of organization objects for my 1 organization in the same registry..
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 25 mei 2018, om 22:38 heeft Antoin Verschuren het volgende
geschreven:
> Hi Ja
se case, I would agree with you.
It may look like overdesigning now if that were the only use case, but if we
don’t add structure now, it will be hard to go back once unstructured objects
are already populated.
We took the challenge of doing more work now, to have quicker innovation later.
And I
ant extra work, but
third party dns-operators, ICANN related policy makers, RIR’s, registrants and
plain IETF protocol guardians also have an equal voice in the IETF process,
even though they don’t implement.
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
signa
Antoin Verschuren has requested publication of
draft-ietf-regext-rdap-object-tag-03 as Best Current Practice on behalf of the
REGEXT working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-objec
?
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 25 mei 2018, om 17:25 heeft Roger D Carney het
volgende geschreven:
> Good Morning,
>
> Do we need to discuss our next documents in our regular meeting slot?
>
> For the regular meeting, I would
Scott,
Sounds like an excellent idea.
Since it’s new work, I assume we would like to have that discussion in our
"work session”?, and Francisco is willing to lead that discussion?
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 30 mei 2018, om 20:19
, Agenda
Co-chairs: Jim Galvin, Antoin Verschuren
Mailinglist: regext@ietf.org
*
Session I, Work session.
?? 2h
1. Unhandled Namespaces (Jim Gould, 40 min.)
2. Registry Mapping (Roger Carney, 40 min.)
3. RDAP Search Capabilities and Authentication
scusion on the
mailinglist and we will also have an item on our agenda in Montreal to discuss.
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
Op 13 jun. 2018, om 23:39 heeft Andrew Newton het volgende
geschreven:
> Thanks for the clarification, Roger.
Antoin Verschuren has requested publication of
draft-ietf-regext-allocation-token-08 as Proposed Standard on behalf of the
REGEXT working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-regext-allocation-
Antoin Verschuren has requested publication of draft-ietf-regext-org-08 as
Proposed Standard on behalf of the REGEXT working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-regext-org/
___
regext mailing
Antoin Verschuren has requested publication of draft-ietf-regext-org-ext-07 as
Proposed Standard on behalf of the REGEXT working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-regext-org-ext/
___
r
version we resend to
the IESG for reconsideration.
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
> Op 3 sep. 2018, om 17:31 heeft Alexander Mayrhofer
> het volgende geschreven:
>
> Hello everyone,
>
> tl;dr - i do agree with all what Patrick
publication process, and we will
send a revised charter to the IESG next week.
Is there any need for a work session now that most documents that needed
discussion have proceeded and the new items have not been presented yet?
Thanks,
Jim and Antoin
- --
Antoin Verschuren
Tweevoren 6, 5672 SB
ee that that
may be in scope by the text that you propose and that that would be undesirable?
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
signature.asc
Description: Message signed with OpenPGP
___
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
I personally think it does too. At least I wrote the text to include those
documents in scope.
But since I’m not a native english speaker it would help to know if others read
that text the same way too.
And confirm it’s not too broad in scope too.
- --
Antoin Verschuren
Tweevoren 6, 5672 SB
from WG participants that
couldn’t make Monday).
- --
Antoin Verschuren
Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392
> Op 19 sep. 2018, om 23:40 heeft Gould, James
> het volgende geschreven:
>
> We can add the login security extension (draft-gould-regext-login-security)
1 - 100 of 226 matches
Mail list logo