IETF Logo Mail Archive

[mif] Question about draft-liu-mif-api-extension-06

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 16 December 2011 02:02 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE7811F0C61 for <mif@ietfa.amsl.com>; Thu, 15 Dec 2011 18:02:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.567
X-Spam-Level:
X-Spam-Status: No, score=-103.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fhYsYQTBS07z for <mif@ietfa.amsl.com>; Thu, 15 Dec 2011 18:02:30 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6CE6D1F0C48 for <mif@ietf.org>; Thu, 15 Dec 2011 18:02:30 -0800 (PST)
Received: by wgbdr13 with SMTP id dr13so4018179wgb.13 for <mif@ietf.org>; Thu, 15 Dec 2011 18:02:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=Pj5zK73bRiT+6s2n1fdYmySTOKe96WCEKOAKTieJbWc=; b=j6BotIoaUUs+t+M4Gs2kN8p8f8nwcDjRRDL74tXVdorBloOvgQKNyCeG8hgztJ10zq njC+BgsRRaqyFZSbPDN5Y9PnTpu2Ei35rjcQm+X+PBuu0KMgq10Gobx9Dc7uaVCeFYmf kE/4JA9abvagVNAjH3Ik7XVkXlwuUGrFe/+AA=
Received: by 10.180.93.228 with SMTP id cx4mr9613654wib.19.1324000949650; Thu, 15 Dec 2011 18:02:29 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id ei9sm11051599wid.0.2011.12.15.18.02.28 (version=SSLv3 cipher=OTHER); Thu, 15 Dec 2011 18:02:29 -0800 (PST)
Message-ID: <4EEAA6BC.7060402@gmail.com>
Date: Fri, 16 Dec 2011 15:02:36 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: mif@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Subject: [mif] Question about draft-liu-mif-api-extension-06
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 02:02:31 -0000

I realise that this is a description of a conceptual API, not a concrete one,
but I still have a concrete question.

A provisioning domain is defined in RFC 6418 as
"A set of consistent configuration information (e.g., default
router, network prefixes, DNS) and the corresponding interface."

Don't we need a notion of Provisioning Domain Identifier to
go with that? Interfaces are identified by Zone Identifiers
according to RFC 4007. Is there any reason that the existing concept
of Zone Identifier can't be extended to cover provisioning domains?

I would like some clarity about this, to ensure that
draft-carpenter-6man-uri-zoneid is also valid for MIF.

Regards
   Brian Carpenter

v2.23.0 | Report a Bug | By Email