Re: [Bundled-domain-names] A lightweight and semantics-free proposal to signal aliasing

> Shouldn't DNAMEs in the parent zone work for this?

Now that you mention it, they should, give or take the well known problems 
with NS and MX.

>
> Sent from my iPhone
>
>> On Nov 9, 2016, at 04:37, John Levine <johnl@taugh.com> wrote:
>>
>> In article <20161114131643.GA13407@laperouse.bortzmeyer.org> you write:
>>> -=-=-=-=-=-
>>>
>>> Following the discussion this evening in Seoul. If you have time to
>>> read it before the BoF on Wednesday...
>>>
>>> I'll formally present it at the BoF if there is interest.
>>
>> If the goal is to alias trees, I don't understand how clients would
>> use it.  Let's say you do this:
>>
>> other.example. ALIAS main.example.
>>
>> main.example. SAILA other.example.
>>
>> Now I look up www.other.example, which I presume is supposed to be
>> substitutable for www.main.example.  How can I tell that one is
>> the alias for the other?  Tree walk?  Magic extra stuff in the
>> DNS response?  Something else?
>>
>> Signed,
>> Confused
>>
>> PS: This proposal looks a lot like a simpler version of Andrew's SOPA
>> proposal, which solved the problem by requiring a SOPA record at every
>> substitutable name.
>>
>> _______________________________________________
>> Bundled-domain-names mailing list
>> Bundled-domain-names@ietf.org
>> https://www.ietf.org/mailman/listinfo/bundled-domain-names
>
>

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly