On November 3, 2018 4:24:31 AM UTC, "Murray S. Kucherawy"
wrote:
>On Sat, Nov 3, 2018 at 12:44 PM Scott Kitterman
>wrote:
>
>> >Sorry, what's being deleted? RFC7601bis doesn't (shouldn't!) be
>> >deleting
>> >anything; it adds a couple of entries and makes itself authoritative
>> >for
>>
On Sat, Nov 3, 2018 at 12:44 PM Scott Kitterman
wrote:
> >Sorry, what's being deleted? RFC7601bis doesn't (shouldn't!) be
> >deleting
> >anything; it adds a couple of entries and makes itself authoritative
> >for
> >the registration of the header field, but otherwise nothing is
> >changing. I
On November 3, 2018 3:25:15 AM UTC, "Murray S. Kucherawy"
wrote:
>On Thu, Oct 25, 2018 at 8:03 PM Alexey Melnikov
>
>wrote:
>
>> 1) I am not sure that deleted IANA registry descriptions (when
>compared
>> to RFC 7601) is the best way, considering that this document
>obsoletes
>> RFC 7601. I
On Thu, Oct 25, 2018 at 8:03 PM Alexey Melnikov
wrote:
> 1) I am not sure that deleted IANA registry descriptions (when compared
> to RFC 7601) is the best way, considering that this document obsoletes
> RFC 7601. I think it would be better to just keep the text and add a
> sentence saying that
On Sat 27/Oct/2018 02:33:27 +0200 Brandon Long wrote:
> should authserv-id bet a dot-atom instead? That seems to be the main uses I
> see, as a domain, and that would allow UTF-8.
That was also discussed at the time of rfc5451bis:
In article <3eea2f77-8aea-4f49-80f3-d96b639c3...@isode.com> you write:
> Note that in an EAI-formatted message, this identifier may be
> expressed in UTF-8.
>
>So I decided to check whether this statement is actually true.
Oops.
>OLD:
>
>"value" is as defined in Section 5.1 of [MIME].
Hi,
I've started IETF LC on the document, as my comments are really minor:
1) I am not sure that deleted IANA registry descriptions (when compared
to RFC 7601) is the best way, considering that this document obsoletes
RFC 7601. I think it would be better to just keep the text and add a
