Re: [Cbor] changes in draft-ietf-cbor-network-addresses-05.txt

On 25-Jul-21 13:37, Michael Richardson wrote:
> 
> Erik Kline <ek.ietf@gmail.com> wrote:
>     > Was there any interest in figuring out a representation for link-local
>     > addresses (e.g. 169.254.x.y, fe80::zed, ff02::pqr, ...) that included
>     > either an interface name or index as part of a structured unit?  Perhaps
>     > some generic {address_info, interface_info} pairing that could be 
used the
>     > same way?
> 
> We will name the third form "Interface Format" or "Inteface Definition Format"
> 
> I think that the concern about the scope could only apply to that format,
> or to the Address format.
> Hmm. Well, the more I think about it, the more I think it applies to Address only.
> 
> I imagine we might find a way to do this differently.
> Best I think think about is abusing maps in some way here.
>      { 'eth0' => h'fe800db81234DEEDBEEFCAFEFACEFEED' }
> 
>     > Obviously, it's possible to pair what you've described here together with
>     > extra interface information separately on an ad hoc basis.
> 
> I'd like to avoid inventing syntax before we need it.
> So, let's talk about how you might use this?

Indeed. I can more easily imagine how core-href might need
it, because the use cases for http might conceivably apply
there. But I don't see it here.

It would be an easy extension, just add a field to the array,
so could we just leave it for later?

fwiw, in a constrained environment, I think you'd always want
to use the interface number (a small integer) rather than
the interface name (which can be a lot longer than "eth0";
"enxb827ebc170a4" is a real example from my Raspberry Pi).

   Brian

> I heard a talk about Extended ICMP Echo from Ron Bonica this week, and I can
> see how it might have used it, but that ship has sailed.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>            Sandelman Software Works Inc, Ottawa and Worldwide
> 
> 
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor
> 