Re: [netmod] Address Family versus Address Family

Ladislav Lhotka <lhotka@nic.cz> Wed, 21 November 2018 12:13 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6B2212F18C for <netmod@ietfa.amsl.com>; Wed, 21 Nov 2018 04:13:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5-Qm8niEIXFf for <netmod@ietfa.amsl.com>; Wed, 21 Nov 2018 04:13:33 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id A0E8A1298C5 for <netmod@ietf.org>; Wed, 21 Nov 2018 04:13:28 -0800 (PST)
Received: by trail.lhotka.name (Postfix, from userid 109) id 64E9A182113D; Wed, 21 Nov 2018 13:20:56 +0100 (CET)
Received: from localhost (unknown [195.113.220.121]) by trail.lhotka.name (Postfix) with ESMTPSA id 60156182113A; Wed, 21 Nov 2018 13:20:42 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: tom petch <ietfc@btconnect.com>, "netmod\@ietf.org" <netmod@ietf.org>
In-Reply-To: <033101d4818e$08689dc0$4001a8c0@gateway.2wire.net>
References: <033101d4818e$08689dc0$4001a8c0@gateway.2wire.net>
Mail-Followup-To: tom petch <ietfc@btconnect.com>, "netmod\@ietf.org" <netmod@ietf.org>
Date: Wed, 21 Nov 2018 13:13:07 +0100
Message-ID: <87wop6sk6k.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/5s_pYzqomMIRs1fD3DEWBnV85TI>
Subject: Re: [netmod] Address Family versus Address Family
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2018 12:13:38 -0000

tom petch <ietfc@btconnect.com> writes:

> I have always thought of Address Family as something that BGP created
> and that others have used.  In fact, I find that there is an IANA
> registry of Address Families which RFC8294 has turned into a YANG
> module, but one using enumeration and not identity, which would seem to
> limit its utility.

In draft-lhotka-dnsop-iana-class-type-yang-00 we also use enumerations
representing DNS classes and resource records types. However, in
addition to the enumeration type that reflects the corresponding IANA
registries, we also added a union type that allows for using either the
mnemonic name or assigned number:

typedef rr-type {
  type union {
    type uint16;
    type rr-type-name;
  }
}

(and similarly for DNS classes). The numeric value corresponding to each
mnemonic name is given by the "value" statement inside each enum.

Actually, this approach was suggested by RFC 3597 that introduced the
general possibility of representing DNS classes and RR types
numerically. For example, RR type "AAAA" can be equivalently represented
as "TYPE28".

Perhaps this approach could be used for address families as well. In
fact, the use of identities also has its share of problems.

Lada

>
> Indeed, while the lsr WG uses that module, I2RS does not with
>  draft-ietf-i2rs-rib-data-model
> defining
>    identity address-family {description  "Base identity from which all
> RIB      address families are derived.";  }
>
> identity - good; RYO definition - um.
>
> BGP also goes its own way with
>   identity AFI_SAFI_TYPE { description
>          "Base identity type for AFI,SAFI tuples for BGP-4";
>        reference "RFC4760 - multi-protocol extensions for BGP-4";  }
>
> And then there is RFC8349 with
>   identity address-family {
>     description  "Base identity from which identities describing address
>           families are derived.";      }
> and which defines ipv4 and ipv6, and which ties the concept firmly to a
> RIB in a 1:1 correspondence.
>
> When I raised this on the rtgwg list, the response was that the concept
> of an address family is particular to a protocol, so there is no reason
> for ospf and BGP to share anything, which is how it seems.
>
> So, is there any reason for anyone to use the definition in RFC8349? or
> the IANA module?
>
> Tom Petch
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67