On 3 March 2017 at 14:36, Gould, James wrote:
> Antoin,
>
> I’m willing to help facilitate or participate in the reseller drafts
> (draft-ietf-regext-reseller and draft-ietf-regext-reseller-ext) sub-group;
> although the draft-ietf-regext-epp-fees sub-group is a high priority for me.
> You may
Hi there,
Another question
1) country (full name / name) versus country codes.
In https://tools.ietf.org/html/rfc7483#section-3 you suggest to use
alpha-2 country codes
Yet autnum and network talk about
---8<---
o country -- a string containing the name of the two-character
country code
On 21 March 2017 18:47:34 CET, Andrew Newton wrote:
>Hi...
>
>On Sun, Mar 19, 2017 at 12:55 PM, Bernhard Reutner-Fischer
> wrote:
>> Hi there,
>>
>> Another question
>>
>> 1) country (full name / name) versus country codes.
>>
>> In https://to
Hi!
3) missing normative reference to IANA, "RDAP JSON Values" ?
https://tools.ietf.org/html/rfc7483#section-10.2.2
mentions
---8<---
... have been registered in the "RDAP JSON Values"
registry:
---8<---
But there is no reference (rendered?) to rdap-json-values in
https://tools.ietf.org/html/
On 22 March 2017 at 12:08, Thomas Corte wrote:
> 1) There seem to be contradictory requirements regarding the handling of
> invalid currency codes. In section 3.2, the draft says:
>
> "Servers SHOULD NOT perform a currency conversion if a client uses an
>incorrect currency code. Servers SH
On 23 March 2017 16:38:31 CET, Andrew Newton wrote:
>On Tue, Mar 21, 2017 at 3:47 PM, Bernhard Reutner-Fischer
> wrote:
>>>> 2) entity handles
>>>>
>>>> At least for DNRs the mixture of registrars and contacts seems to
>be
>>>a
>>>
On 24 March 2017 11:05:44 CET, Thomas Corte wrote:
>Hello Bernhard,
>
>On 23/03/2017 16:04, Bernhard Reutner-Fischer wrote:
>
>> In my view 2004 is more on the protocol-layer, i.e. value supplied
>not in
>> curl -s -o-
>https://www.currency-iso.org/dam/downloads/lis
On 22 March 2017 at 13:58, Bernhard Reutner-Fischer
wrote:
> Hi!
>
> 3) missing normative reference to IANA, "RDAP JSON Values" ?
>
> https://tools.ietf.org/html/rfc7483#section-10.2.2
> mentions
> ---8<---
> ... have been registered in the "RDAP JSON
On 3 April 2017 16:21:55 CEST, Andrew Newton wrote:
>On Fri, Mar 31, 2017 at 4:08 AM, Bernhard Reutner-Fischer
> wrote:
>> On 22 March 2017 at 13:58, Bernhard Reutner-Fischer
>> 4) Domain object, secureDNS/delegationSigned
>>
>> ---8<---
>> * delega
On 3 April 2017 20:44:34 CEST, Andrew Newton wrote:
>On Mon, Apr 3, 2017 at 12:56 PM, Bernhard Reutner-Fischer
> wrote:
>> PS: can you please answer the other question too?
>
>Can you restate your questions? I'm unsure what is being asked.
Shouldn't there be a refere
On 14 March 2016 at 16:51, Hollenbeck, Scott wrote:
>> -Original Message-
>> From: IETF-Announce [mailto:ietf-announce-boun...@ietf.org] On Behalf
>> Of The IESG
>> Sent: Monday, March 14, 2016 11:19 AM
>> To: IETF-Announce
>> Cc: eppext-cha...@ietf.org; draft-ietf-eppext-tmch-...@ietf.org
On 10 July 2017 10:50:44 CEST, Bernhard Reutner-Fischer
wrote:
>On 14 March 2016 at 16:51, Hollenbeck, Scott
>wrote:
>>> -Original Message-
>>> From: IETF-Announce [mailto:ietf-announce-boun...@ietf.org] On
>Behalf
>>> Of The IESG
>>> Sent:
On 3 April 2017 at 19:56, Bernhard Reutner-Fischer
wrote:
> On 3 April 2017 16:21:55 CEST, Andrew Newton wrote:
>>On Fri, Mar 31, 2017 at 4:08 AM, Bernhard Reutner-Fischer
>> wrote:
>>> On 22 March 2017 at 13:58, Bernhard Reutner-Fischer
>>> 4) Domain o
On 12 October 2016 at 02:46, Francisco Arias wrote:
> FYI,
>
>
>
> There is an updated proposal to handle the RySG proposed revision to the
> CL&D policy to remove the requirement to implement RDAP. We are planning to
> put a draft updated CL&D policy for public comment before the end of the
> mon
On 23 March 2017 at 19:38, Bernhard Reutner-Fischer
wrote:
> On 23 March 2017 16:38:31 CET, Andrew Newton wrote:
>>On Tue, Mar 21, 2017 at 3:47 PM, Bernhard Reutner-Fischer
>> wrote:
>>>>> 2) entity handles
>>>>>
>>>>> At least for DNR
On 13 September 2017 at 01:17, Francisco Arias
wrote:
> Thank you for the suggestion, Bernhard. We'll take it into consider if the
> document is revived, as you said.
>
> --
> Francisco
>
> On 9/12/17, 2:00 AM, "Bernhard Reutner-Fischer" wrote:
>
On 12 September 2017 at 10:22, Bernhard Reutner-Fischer
wrote:
> On 3 April 2017 at 19:56, Bernhard Reutner-Fischer
> wrote:
>> On 3 April 2017 16:21:55 CEST, Andrew Newton wrote:
>>>On Fri, Mar 31, 2017 at 4:08 AM, Bernhard Reutner-Fischer
>>> wrote:
>>&g
On 21 September 2017 at 22:11, Bernhard Reutner-Fischer
wrote:
> On 12 September 2017 at 10:22, Bernhard Reutner-Fischer
> wrote:
>> On 3 April 2017 at 19:56, Bernhard Reutner-Fischer
>> wrote:
>>> On 3 April 2017 16:21:55 CEST, Andrew Newton wrote:
>>
On 29 September 2017 18:15:32 CEST, Andrew Newton wrote:
>Antoin,
>
>Sorry for being late with this but I wasn't sure I'd get the document
>updated in time.
>
>The topic of RDAP and schemas came up in the last meeting. If
>possible, I'd like to discuss
>draft-newton-rdap-jcr.
>https://datatracker.
On 12 February 2018 15:29:02 CET, "Hollenbeck, Scott"
wrote:
>> -Original Message-
>> From: regext [mailto:regext-boun...@ietf.org] On Behalf Of internet-
>> dra...@ietf.org
>> Sent: Tuesday, January 16, 2018 8:50 AM
>> To: i-d-annou...@ietf.org
>> Cc: regext@ietf.org
>> Subject: [EXTERNA
On 23 January 2018 at 20:32, Amanda Baber via RT wrote:
The description of "result set truncated due to authorization" has a typo:
s/thaadt/that/
according to https://tools.ietf.org/html/rfc7483#section-10.2.1
In
"... to some clients thaadt proper authorization ..."
replace "thaadt" with "that
On Tue, 19 Sep 2017 at 18:36, Bernhard Reutner-Fischer
wrote:
>
> On 13 September 2017 at 01:17, Francisco Arias
> wrote:
> > Thank you for the suggestion, Bernhard. We'll take it into consider if the
> > document is revived, as you said.
> >
> > --
>
On 18 February 2019 12:18:37 CET, Gavin Brown
wrote:
>After some private discussions, I've come up with a rough draft of a
>document specifying an alternative representation of contact data for
>RDAP entities that does away with vCard, and uses the model from EPP
>instead:
>
>https://tools.ietf.o
On Wed, 25 Mar 2020 10:29:52 +0100
Alexander Mayrhofer wrote:
> Hello everyone,
>
> Ulrich has published a new revision of his registry lock draft
> (draft-wisser-registrylock). We're currently in the
In 4.2.5. EPP Command
s/SEVER_UPDATE_PROHIBITED/serverUpdateProhibited/
> I know that - as
On Thu, 2 Dec 2021 07:45:24 -0800 (PST)
RFC Errata System wrote:
> The following errata report has been verified for RFC7484,
> "Finding the Authoritative Registration Data (RDAP) Service".
>
> --
> You may review the report below and at:
> https://www.rfc-e
On 21 April 2022 16:35:25 CEST, "Gould, James"
wrote:
>+1 on the use 2103/"Unimplemented extension". This is a broader topic with
>the passing invalid or conflicting extensions (e.g., restore request extension
>of update along with the sync extension).
>
2103 would suggest that the extensio
26 matches
Mail list logo
