[grobj] NATs and scope

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 19 November 2009 20:21 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: grobj@core3.amsl.com
Delivered-To: grobj@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D18F33A6A0E for <grobj@core3.amsl.com>; Thu, 19 Nov 2009 12:21:34 -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=[AWL=0.000, 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 5FNR4aGGH3uL for <grobj@core3.amsl.com>; Thu, 19 Nov 2009 12:21:34 -0800 (PST)
Received: from mail-pz0-f176.google.com (mail-pz0-f176.google.com [209.85.222.176]) by core3.amsl.com (Postfix) with ESMTP id 187043A6A0D for <grobj@ietf.org>; Thu, 19 Nov 2009 12:21:34 -0800 (PST)
Received: by pzk6 with SMTP id 6so1757729pzk.29 for <grobj@ietf.org>; Thu, 19 Nov 2009 12:21:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=oXQzGI2hkD66Dx7zidrGkoZc0H6od0z8udvi/w4t5PI=; b=APn3FPRYSVgMT2nUWTotYkU1KRJQe5DTkkAdsEGCAEY5Z9EesFfNklslwovJv9Akj9 XxR+v/BNNYlHgOz40Hbo3FzUdLdn3Qz2XLxP1y44o0xJi56jfmHWwa8ygc4dX7gcgwls rUrCrFiuc2+XBfi8/0OhRSpKQlOfjhUjHODaA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=C6s2DI6uzEn6KP1oGLhaM+Bkd3K/cmnnQqalX1SjToDDstc9xFzkBJvgcW4YPi7WS5 rjE4BqbfyIHsB3AUGw9BIWYD1l17x23uCfLOHzmt8C5s1no9fI+kvGbi4J/hsKiaHEWp ACYPNlk7aKVfus1591DhJfwSkic155JIQSvhc=
Received: by 10.115.112.40 with SMTP id p40mr427465wam.182.1258662089529; Thu, 19 Nov 2009 12:21: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 20sm531839pzk.9.2009.11.19.12.21.28 (version=SSLv3 cipher=RC4-MD5); Thu, 19 Nov 2009 12:21:29 -0800 (PST)
Message-ID: <4B05A8CD.5020804@gmail.com>
Date: Fri, 20 Nov 2009 09:21:33 +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: Simon Perreault <simon.perreault@viagenie.ca>
References: <4AFA91BF.2010808@viagenie.ca> <4AFB497D.1080901@employees.org> <4B055227.3090902@viagenie.ca>
In-Reply-To: <4B055227.3090902@viagenie.ca>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: grobj@ietf.org
Subject: [grobj] NATs and scope
X-BeenThere: grobj@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discuss Generic Referral Objects <grobj.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/grobj>, <mailto:grobj-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grobj>
List-Post: <mailto:grobj@ietf.org>
List-Help: <mailto:grobj-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grobj>, <mailto:grobj-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Nov 2009 20:21:34 -0000

On 2009-11-20 03:11, Simon Perreault wrote:

> - The "scope" of an address (I'm still not fully understanding the concept) does
> not guarantee that that the address is reachable from anyone in that scope. For
> example, the address of a NAT binding (called a "reflexive transport address" in
> RFC5389) can be reached by a subset of peers in the NAT's scope which depends on
> the type of NAT (see e.g. RFC4787 for types of NATs).

So, given what I just said about scope (with no reference to NATs), I think
Simon needs to tell us what he means by "in the NAT's scope".

To me an address scope is a set of mutually reachable addresses, which
means that a NAT automatically forms (part of) the boundary of a scope.
I don't understand what is meant by "a subset of peers" - surely all
the peers behind a given NAT (more precisely, behind a given interface
of a given NAT) are in the same address space?

   Brian