Are we sure that all the use cases for this AFI fall into the ASCII
character set. DNS names clearly do meet that restriction. But many
other names do not. And while people can and do define escapes, it
produces complicated and messy situations.
I ask because as defined, even if we wanted to, this can not be used to
carry UTF-8 to the fact that bytes of all 0 may occur in UTF-8.
There are many good reasons to keep this simple scope. If we want to
keep that restrictions, it seems to me that the introduction should be
clear about the scope.
Yours,
Joel M. Halpern
On 10/3/16 12:28 PM, Dino Farinacci wrote:
Folks, I am going to update this draft so it doesn’t expire. At this time, I
would like to request this a working group document. It is a very simple draft
and would like to see if there are any comments and if we can start a last call
on it. Chairs?
Dino
Begin forwarded message:
From: IETF Secretariat <[email protected]>
Subject: Expiration impending: <draft-farinacci-lisp-name-encoding-00.txt>
Date: October 3, 2016 at 4:42:10 AM PDT
To: <[email protected]>
Resent-From: <[email protected]>
Resent-To: [email protected]
The following draft will expire soon:
Name: draft-farinacci-lisp-name-encoding
Title: LISP Distinguished Name Encoding
State: I-D Exists
Expires: 2016-10-15 (in 1 week, 4 days)
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
