Re: [DNSOP] Character encoding of URI Target RDATA?

Robert Edmonds wrote: > > What I'm asking is how the octet sequences provided by the URI RR RFC > are decoded into the sequences of URI characters used by the URI RFC. > Is there a generic way to do this, or does it depend on the specific > protocol (e.g., HTTP), or is it left up to the applicatio

Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-terminology-02.txt

On Mon, Jun 15, 2015 at 11:49:47AM -0700, Paul Hoffman wrote: > > "Name Error" as a synonym for NXDOMAIN seems like it is worth including, > > somewhere. > > Are you sure that "name error" always refers to NXDOMAIN? If not, this is not > a can of worms we should open. > To the extent it doesn

Re: [DNSOP] Character encoding of URI Target RDATA?

Patrik Fältström wrote: > On 16 Jun 2015, at 22:45, Robert Edmonds wrote: > >John Levine wrote: > >>Can you give an example of URI RDATA where it would make sense to > >>interpret it other than as ASCII? > > > >This is the FTP example from the URI RR RFC, to which the UTF-8 byte order > >mark has b

Re: [DNSOP] Character encoding of URI Target RDATA?

Tony Finch wrote: > Robert Edmonds wrote: > > > > What I'm asking is how the octet sequences provided by the URI RR RFC > > are decoded into the sequences of URI characters used by the URI RFC. > > Is there a generic way to do this, or does it depend on the specific > > protocol (e.g., HTTP), or i

Re: [DNSOP] I-D Action: draft-ietf-dnsop-qname-minimisation-03.txt

On Thu, Jun 11, 2015 at 07:39:20PM -0700, Paul Hoffman wrote a message of 41 lines which said: > We sometimes forget that people have heard that every dot makes a > new level in the DNS I don't think it was forgotten here. The current section 2 of -03 (the text quoted by Tony) clearly says th

Re: [DNSOP] Character encoding of URI Target RDATA?

On Wed, Jun 17, 2015 at 12:38:22PM +0900, Masataka Ohta wrote: > > What I'm asking is how the octet sequences provided by the URI RR RFC > > The RFC does not provide the octet sequences. Zone files do. This is indeed correct. We can ignore what characters are in the URI and just stuff them in the

Re: [DNSOP] I-D Action: draft-ietf-dnsop-qname-minimisation-03.txt

On Fri, Jun 12, 2015 at 01:54:50AM +0100, Tony Finch wrote a message of 44 lines which said: > (end) I do not completely agree with the change but I hope I was able to address your concern. See the diff in

Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-terminology-02.txt

On Jun 17, 2015, at 9:03 AM, Andrew Sullivan wrote: > > On Mon, Jun 15, 2015 at 11:49:47AM -0700, Paul Hoffman wrote: > >>> "Name Error" as a synonym for NXDOMAIN seems like it is worth including, >>> somewhere. >> >> Are you sure that "name error" always refers to NXDOMAIN? If not, this is >

Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-terminology-02.txt

On Jun 16, 2015, at 3:33 AM, John Dickinson wrote: > > > > On 15/06/2015 22:35, Paul Hoffman wrote: > "NSEC3": whether not NSEC3 is "quite different" from NSEC depends on your > context. Functionally, in the narrow sense of "allows verifiable denial > of existence", they are ident

Re: [DNSOP] Character encoding of URI Target RDATA?

On 17 Jun 2015, at 16:52, bert hubert wrote: > At least if the RFC does not specify it, we should pick something. The over arching issue here is that there is no right answer regarding non ascii in URIs. A URI is a sequence of characters, but in HTTP the path must be ascii only, and can have %

Re: [DNSOP] I-D Action: draft-ietf-dnsop-dns-terminology-02.txt

On Jun 16, 2015, at 3:50 AM, Tony Finch wrote: > > Paul Hoffman wrote: >> >>> "Name Error" as a synonym for NXDOMAIN seems like it is worth >>> including, somewhere. >> >> Are you sure that "name error" always refers to NXDOMAIN? If not, this >> is not a can of worms we should open. > > Absol

Re: [DNSOP] Character encoding of URI Target RDATA?

bert hubert wrote: > How do we encode this in a zonefile? The checkmark is Unicode 0x2713, but > encoded as UTF-8 it is 0xe2 0x9c 0x93, or 226 156 147. See my first response. Masataka Ohta ___ DNSOP mail