RE: [saad] About saad

"Michel Py" <michel@arneill-py.sacramento.ca.us> Fri, 17 October 2003 16:55 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10204 for <saad-archive@odin.ietf.org>; Fri, 17 Oct 2003 12:55:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAXsU-0006cy-W6 for saad-archive@odin.ietf.org; Fri, 17 Oct 2003 12:55:03 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h9HGt2JZ025470 for saad-archive@odin.ietf.org; Fri, 17 Oct 2003 12:55:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAXsU-0006cj-R4 for saad-web-archive@optimus.ietf.org; Fri, 17 Oct 2003 12:55:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10176 for <saad-web-archive@ietf.org>; Fri, 17 Oct 2003 12:54:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAXsT-0005Zo-00 for saad-web-archive@ietf.org; Fri, 17 Oct 2003 12:55:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AAXsS-0005Zl-00 for saad-web-archive@ietf.org; Fri, 17 Oct 2003 12:55:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAXsT-0006bk-F0; Fri, 17 Oct 2003 12:55:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AAXrq-0006X3-Bi for saad@optimus.ietf.org; Fri, 17 Oct 2003 12:54:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10122 for <saad@ietf.org>; Fri, 17 Oct 2003 12:54:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AAXro-0005YW-00 for saad@ietf.org; Fri, 17 Oct 2003 12:54:20 -0400
Received: from adsl-209-233-126-65.dsl.scrm01.pacbell.net ([209.233.126.65] helo=arneill-py.sacramento.ca.us) by ietf-mx with esmtp (Exim 4.12) id 1AAXro-0005Xk-00 for saad@ietf.org; Fri, 17 Oct 2003 12:54:20 -0400
Subject: RE: [saad] About saad
Date: Fri, 17 Oct 2003 09:53:48 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Message-ID: <DD7FE473A8C3C245ADA2A2FE1709D90B06C666@server2003.arneill-py.sacramento.ca.us>
Content-class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: [saad] About saad
thread-index: AcOUxMTRzVdxm9knRQi2wwPjA+ul+gABVmsg
From: "Michel Py" <michel@arneill-py.sacramento.ca.us>
To: "James Kempf" <kempf@docomolabs-usa.com>, "Fred Baker" <fred@cisco.com>
Cc: <saad@ietf.org>
Content-Transfer-Encoding: quoted-printable
Sender: saad-admin@ietf.org
Errors-To: saad-admin@ietf.org
X-BeenThere: saad@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/saad>, <mailto:saad-request@ietf.org?subject=unsubscribe>
List-Id: Scope Addressing Architecture Discussion <saad.ietf.org>
List-Post: <mailto:saad@ietf.org>
List-Help: <mailto:saad-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/saad>, <mailto:saad-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Folks,


> James Kempf wrote:
> The DNS is a node identifier, but it currently can't be used by
> the transport layer as a connection endpoint identifier.

Nor by the network layer.


> Brian E Carpenter wrote:
> The reasons why FQDNs are imperfect EIDs have been listed quite
> recently (on one of the IPV6 lists I think).

Indeed. Besides, what we are talking about is scoping, and one of the
things that is totally in scope is to discuss at which layer(s) scoping
shall occur.


IMHO, scoping shall occur at the IP layer. The fact of the matter is (as
this discussion as shown) it seems that scoping is tied to the
identifier. I think that one of the sound discussions we should have is
to identify if indeed this is true. My vote is yes.

Now, _if_ the identifier is moved above the network layer, and if scope
is tied to the identifier as we might or might not decide it is, we
suddenly have a layer violation, because scope is going to be used at
the routing layer (the IP layer) and for the same reason routing must
not use DNS (because DNS needs routing) we will likely bump into the
issue that scope could not use {whatever the identifier in an upper
layer is} because of the same circular reference issue.

So, IMHO the beginning of the decision tree is:

     |
     v
     |
     /\
    /  \
   / Is \          +----------------------------+
  /scope \         | Since we don't have        |
 /  tied  \        | identifiers at another     |
/ to the   \  yes  | layer than IP now,         |
\identifier/--->---+ scoping is to be done      |
 \or not? /        | at the network layer.      |
  \      /         | if we ever get identifiers |
   \    /          | in other layers, situation |
    \  /           | will be revisited then.    |
     \/            +----------------------------+
     |
     v  no
     |
+----+----------+
| what are the  |
| reasons to    |
| move scope to |
| another layer |
| than IP?      |
+----+----------+
     |
     | ???
     |


Comments?

Michel.


_______________________________________________
Saad mailing list
Saad@ietf.org
https://www1.ietf.org/mailman/listinfo/saad