As pointed out by others, this is what I proposed back in July '21:

typedef ipv6-address-link-local {
  type ipv6-address;
  pattern '[fF][eE]80:.*';
  description
    "A link-local IPv6 address in the prefix fe80::/10 as defined
     in section 2.5.6. of RFC 4291.";
  reference
    "RFC 4291: IP Version 6 Addressing Architecture";
}

If this serves the purpose, I can add this definition to the
inet-types module.

Will there also be a need to have an IPv4 equivalent?

typedef ipv4-address-link-local {
  type ipv4-address;
  pattern '169\.254\..*';
  description
    "A link-local IPv4 address in the prefix 169.254.0.0/16 as 
     defined in section 2.1. of RFC 3927.";
  reference
    "RFC 3927: Dynamic Configuration of IPv4 Link-Local Addresses";
}

/js

On Thu, Jan 06, 2022 at 04:54:09PM -0500, Jeffrey Haas wrote:
> Mahesh suggested I send this suggestion here.
> 
> Several IPv6 routing protocols have circumstances where the only acceptable 
> address is an ipv6 link-local address.
> 
> The YANG type we have for ipv6 can accommodate ipv6 link local addresses, 
> however it's overly permissive for some use cases.
> 
> Has the Working Group considered adding a typedef for ipv6 link-local?
> 
> FWIW, the current use case under consideration is operational state for BGP 
> IPv6 routes conforming to RFC 2545 and related work under consideration in 
> IDR for link-local only BGP peering.  In such circumstances, the BGP nexthop 
> will contain a component that may only be ipv6 link-local.
> 
> For the BGP YANG module, the edits under consideration will currently use the 
> ipv6 type.  Since the current use case is operational only state, the lack of 
> the more restrictive type is not considered a blocker. For the future 
> link-local-only work, configuration state will be needed.
> 
> -- Jeff
> 

-- 
Jürgen Schönwälder              Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>

_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to