Re: How to specify InetAddressType COMPLIANCE requirements

[Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>]

On Thu, Jul 31, 2003 at 11:30:40AM +0200, Wijnen, Bert (Bert) wrote:
> 
> I have some people (IPCDN WG) who have (In MODULE-COMPLIANCE):
> 
>    OBJECT diffServMultiFieldClfrAddrType
>       SYNTAX  InetAddressType { ipv4(1) }
>       DESCRIPTION
>          "An implementation is only required to support IPv4
>           addresses."
> 
>       Or possibly a DESCRIPTION text of:
>          "A DOCSIS 1.0, 1.1 or 2.0 implementation is required
>           to support IPv4 addresses at a minimum."
> 
> And I have people (MPLS WG) who have:
> 
>    OBJECT mplsFTNAddrType
>    SYNTAX InetAddressType { ipv4(1), ipv6(2) }
>    DESCRIPTION
>        "An implementation is only required to support IPv4
>         and/or IPv6 addresses.  An implementation is only
>         required to support the address types that are actually
>         supported on the LSR."
> 
> The question here is that people want to express that IPv4 support
> is sufficient for devices that do not (yet) have IPv6 stacks
> but they would want to also indicate that IPv6 support is needed
> (required) if the device DOES have an IPv6 stack. In fact, with
> our IETF drive to make sure that all new specs are both IPv4 and
> IPv6 friendly, we sort of force them to consider IPv6.

Note that scoped link-local addresses are not captured in the compliance
statement on devices that potentially can connect multiple links if you 
restrict the SYNTAX to { ipv4(1) } or { ipv4(1), ipv6(2) }. 

So people should think twice whether it is not good to include 
ipv4z(3) and ipv6z(4) as well so that proper support for link-local
addresses is required on devices which connect multiple links where
conflicts can appear.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany