Re: [PEPPERMINT] Data model for "reachability data" and naming/terminology for group of addresses
Ted Lemon <Ted.Lemon@nominum.com> Wed, 09 July 2008 20:59 UTC
Return-Path: <peppermint-bounces@ietf.org>
X-Original-To: peppermint-archive@optimus.ietf.org
Delivered-To: ietfarch-peppermint-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B18328C1B8; Wed, 9 Jul 2008 13:59:13 -0700 (PDT)
X-Original-To: peppermint@core3.amsl.com
Delivered-To: peppermint@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 204803A69F4 for <peppermint@core3.amsl.com>; Tue, 8 Jul 2008 14:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z1ZRCals1kqt for <peppermint@core3.amsl.com>; Tue, 8 Jul 2008 14:18:04 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7ob114.obsmtp.com [64.18.2.214]) by core3.amsl.com (Postfix) with ESMTP id C4BFD3A689C for <peppermint@ietf.org>; Tue, 8 Jul 2008 14:18:02 -0700 (PDT)
Received: from source ([64.89.228.228]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP; Tue, 08 Jul 2008 14:18:12 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-ng.nominum.com (Postfix) with ESMTP id 3AA031A8203; Tue, 8 Jul 2008 14:18:12 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from exchange-01.WIN.NOMINUM.COM ([64.89.228.50]) by exchange-01.WIN.NOMINUM.COM ([64.89.228.50]) with mapi; Tue, 8 Jul 2008 14:18:11 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Jean-Francois Mule <jf.mule@cablelabs.com>, "Ray.Bellis@nominet.org.uk" <Ray.Bellis@nominet.org.uk>
Date: Tue, 08 Jul 2008 14:18:09 -0700
Thread-Topic: [PEPPERMINT] Data model for "reachability data" and naming/terminology for group of addresses
Thread-Index: AcjXm8RtuZYmIK/fS+aPfBbSQ+ncXAJojV7QAAB2HmA=
Message-ID: <1A6237355F59494CB8CD9791D7F9D1D9059CF18E@exchange-01.WIN.NOMINUM.COM>
References: <9AAEDF491EF7CA48AB587781B8F5D7C601216A72@srvxchg3.cablelabs.com> <OF70AE4588.D4FC8E58-ON80257474.00506742-80257474.00516285@nominet.org.uk> <9AAEDF491EF7CA48AB587781B8F5D7C6012900C4@srvxchg3.cablelabs.com>
In-Reply-To: <9AAEDF491EF7CA48AB587781B8F5D7C6012900C4@srvxchg3.cablelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 09 Jul 2008 13:59:12 -0700
Cc: "peppermint@ietf.org" <peppermint@ietf.org>
Subject: Re: [PEPPERMINT] Data model for "reachability data" and naming/terminology for group of addresses
X-BeenThere: peppermint@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Provisioning Extensions in Peering Registries for Multimedia INTerconnection <peppermint.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/peppermint>
List-Post: <mailto:peppermint@ietf.org>
List-Help: <mailto:peppermint-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/peppermint>, <mailto:peppermint-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: peppermint-bounces@ietf.org
Errors-To: peppermint-bounces@ietf.org
> I believe so. Would folks prefer Destination Group then? As a relative neophyte, it's more obvious to me what "Destination Group" means than what "Service Area" means. So I think it's somewhat preferable, although there's nothing fundamentally wrong with "Service Area." I think it's because "Destination Group" implies logical locality, whereas "Service Area" implies physical locality. _______________________________________________ PEPPERMINT mailing list PEPPERMINT@ietf.org https://www.ietf.org/mailman/listinfo/peppermint
- [PEPPERMINT] Data model for "reachability data" a… Jean-Francois Mule
- Re: [PEPPERMINT] Data model for "reachability dat… Ray.Bellis
- Re: [PEPPERMINT] Data model for "reachability dat… Jean-Francois Mule
- Re: [PEPPERMINT] Data model for "reachability dat… Jean-Francois Mule
- Re: [PEPPERMINT] Data model for "reachability dat… Ted Lemon