Hello,
(re-sending to list)
I would like to find a solution which covers other possible failure modes than
SERVFAIL, too.
Looking at BIND 9.9, it sometimes can return NXDOMAIN or even NOERROR when
validation fails for some obscure reasons.
E.g. an attempt to invent private TLD like 'mycompany'
Paul Hoffman wrote:
> > Regarding specific definitions, what about my suggestions under "more
> > definitions" at
> > http://www.ietf.org/mail-archive/web/dnsop/current/msg14243.html
>
> Some of those definitions were speculative, and I think it is better to
> defer them.
All of the definitions
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 identical. I
think it would be clearer to focus on their functional similarities,
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.
Absolutely. RFC 1035 section 4.1.1:
RCODE Response code -
Masataka Ohta wrote:
> Robert Edmonds wrote:
>
> > What character encoding should be used when decoding the Target field of
> > a URI RR?
>
> It depends on part of URI, which decodes the URI.
No, I'm not talking about the encoding of components within the URI into
URI characters, I'm talking ab
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations Working Group
of the IETF.
Title : Domain Name System (DNS) Cookies
Authors : Donald E. Eastlake
Robert Edmonds wrote:
> This is the *en*coding of characters in a zone file into wire
> data octets.
I'm afraid you are totally confused.
> How should a receiver decode the wire data octets?
Into a zone file? Or?
Masataka Ohta
__
On Tue, Jun 16, 2015 at 12:31 PM, wrote:
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Domain Name System Operations Working
> Group of the IETF.
>
> Title : Domain Name System (DNS) Cookies
> Au
Masataka Ohta wrote:
> Robert Edmonds wrote:
>
> > This is the *en*coding of characters in a zone file into wire
> > data octets.
>
> I'm afraid you are totally confused.
Actually, I don't really see how zone files are relevant to my question.
> > How should a receiver decode the wire data octe
>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 application?
As far as I can see, RFC
John Levine 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 application?
On 16 Jun 2015, at 22:45, Robert Edmonds wrote:
John Levine 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., H
Robert Edmonds wrote:
> Actually, I don't really see how zone files are relevant to my question.
Then, as the only case DNS perform character encoding/decoding
is when it read/write the zone files, you are asking a wrong
questions in a wrong ML.
> What I'm asking is how the octet sequences provi
13 matches
Mail list logo
