Re: [rrg] More abbreviation expansions

Christopher Morrow <morrowc.lists@gmail.com> Sun, 28 February 2010 18:19 UTC

Return-Path: <christopher.morrow@gmail.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD6B228C168 for <rrg@core3.amsl.com>; Sun, 28 Feb 2010 10:19:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 dM2ywozOSUHw for <rrg@core3.amsl.com>; Sun, 28 Feb 2010 10:19:16 -0800 (PST)
Received: from mail-iw0-f195.google.com (mail-iw0-f195.google.com [209.85.223.195]) by core3.amsl.com (Postfix) with ESMTP id BAC9128C14B for <rrg@irtf.org>; Sun, 28 Feb 2010 10:19:16 -0800 (PST)
Received: by iwn33 with SMTP id 33so1800902iwn.23 for <rrg@irtf.org>; Sun, 28 Feb 2010 10:19:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=JfLiL2uJ1T2B3ZzizYR4iQfdaE+NiE0gtb6Xp/GPooU=; b=FFAi3zY7OdK+yhS9u7jfha+54r1y+j73a4O241oevuYlxm6f4FL9sK+3aaehYZlQu9 NjyBjIgdBZnOtevP99tGUXyfWg6WIUG9dFBm3J6GR7/CaUIpsWiM2oRv0SL1tlzwRv6i I83K5pOs68PWg5Y089Dp3jht5KDcm0xZNCIkU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=ZQcVrbd7bKO9NM/pt0Ei+0nZFWcdFr9sAxinPFh0qCBYf5tKPUWwsRhbnCH4AwQ3MF BegZm2RzqCYmhYar60ZrRHzZdWnbDpZl+5V7bXVODyDAPmLQmRz/yLD40qtWkhe88qRC rBCNRRMcRzpkJ64FvU6y7XkGgWadpKMm1/LtE=
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.231.167.204 with SMTP id r12mr104024iby.31.1267381151608; Sun, 28 Feb 2010 10:19:11 -0800 (PST)
In-Reply-To: <4B89B9F7.2010707@gmail.com>
References: <C7ADB85F.3E95%tli@cisco.com> <4B89B9F7.2010707@gmail.com>
Date: Sun, 28 Feb 2010 13:19:11 -0500
X-Google-Sender-Auth: 96816bb4c5318310
Message-ID: <75cb24521002281019w53b81564pd45d935e37679c57@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Tony Li <tli@cisco.com>, RRG <rrg@irtf.org>
Subject: Re: [rrg] More abbreviation expansions
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Feb 2010 18:19:17 -0000

I think either set works, but pick one and stick to it, that's the
important bit.

-chris

On Sat, Feb 27, 2010 at 7:33 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> I have always understood PA to mean Provider Aggregatable
> or Provider Aggregated (which is of course only possible
> because they are assigned by the provider who will perform
> the aggregation).
>
> In terms of history, I have in my archive a note drafted
> in 1995 by Daniel Karrenberg at RIPE, entitled
> "Provider Independent vs Provider Aggregatable Address Space"
> (sent to nanog@merit.edu, cidrd@iepg.org, IANA@isi.edu and
> local-ir@ripe.net on 17 May 1995).
>
> "provider assign[ed]" also pops up in my archive from the same
> era, but "aggregatable" seems to be the more common usage
> (46 vs 18 hits in my archive).
>
> Regards
>   Brian Carpenter
>
> On 2010-02-27 14:41, Tony Li wrote:
>> Hi all,
>>
>> I've received the following proposed text:
>>
>> PA - Provider Assigned: Addresses which cannot be 'taken with you' when a
>> site moves to a different location on the network connectivity
>> structure; usually assigned by a service provider (hence the name).
>>
>> PI - Provider Independent: Addresses associated with a site and which move
>> with it when it moves to a different location on the network connectivity
>> structure; independent of any service provider (hence the name).
>>
>> Any objections?
>>
>> Tony
>>
>> _______________________________________________
>> rrg mailing list
>> rrg@irtf.org
>> http://www.irtf.org/mailman/listinfo/rrg
>>
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg
>