Re: [OFF-PATH-BOF] SIP, naming, APIs and control
Saikat Guha <saikat@cs.cornell.edu> Fri, 14 July 2006 17:35 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1RZ7-0005QQ-NZ; Fri, 14 Jul 2006 13:35:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1RZ5-0005QL-Ly for off-path-bof@ietf.org; Fri, 14 Jul 2006 13:34:59 -0400
Received: from exchfenlb-2.cs.cornell.edu ([128.84.97.34] helo=exchfe2.cs.cornell.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G1RZ4-0000fw-EI for off-path-bof@ietf.org; Fri, 14 Jul 2006 13:34:59 -0400
Received: from sundial.cs.cornell.edu ([128.84.96.115]) by exchfe2.cs.cornell.edu with Microsoft SMTPSVC(6.0.3790.1830); Fri, 14 Jul 2006 13:34:57 -0400
Received: from himalaya.cs.cornell.edu (himalaya.cs.cornell.edu [128.84.223.110]) by sundial.cs.cornell.edu (8.11.7-20031020/8.11.7/M-3.25) with ESMTP id k6EHYuv18553; Fri, 14 Jul 2006 13:34:57 -0400 (EDT)
Subject: Re: [OFF-PATH-BOF] SIP, naming, APIs and control
From: Saikat Guha <saikat@cs.cornell.edu>
To: Teemu Koponen <koponen@ICSI.Berkeley.EDU>
In-Reply-To: <59D9917D-BD2F-4F0C-982C-C9327753A53B@ICSI.Berkeley.EDU>
References: <C0DC1986.10CBB%mshore@cisco.com> <1152894044.13866.213.camel@localhost.localdomain> <59D9917D-BD2F-4F0C-982C-C9327753A53B@ICSI.Berkeley.EDU>
Date: Fri, 14 Jul 2006 18:34:56 +0100
Message-Id: <1152898496.13866.234.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4)
X-OriginalArrivalTime: 14 Jul 2006 17:34:57.0982 (UTC) FILETIME=[D3964DE0:01C6A76B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: off-path-bof@ietf.org
X-BeenThere: off-path-bof@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "BOF: Path-decoupled Signaling for Data" <off-path-bof.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/off-path-bof>, <mailto:off-path-bof-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/off-path-bof>
List-Post: <mailto:off-path-bof@ietf.org>
List-Help: <mailto:off-path-bof-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/off-path-bof>, <mailto:off-path-bof-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0523702092=="
Errors-To: off-path-bof-bounces@ietf.org
On Fri, 2006-07-14 at 09:43 -0700, Teemu Koponen wrote: > On Jul 14, 2006, at 9:20, Saikat Guha wrote: > > _----------S---------_ > > / \ > > / \ > > A --- N --Internet-- M --- B > > Your classification assumes M and N are not explicitly addressed > middleboxes, right? The classification applies more to the signaling protocol than devices themselves. However, the choice of the device may preclude one signaling protocol or another. Here, N and M may or may not be explicitly addressed depending on the nature of the device. If N and M are UPnP/midcom/TURN/SOCKS servers etc., then they need to be addressed explicitly, and for that, some off-path signaling needs to happen first to discover their addresses. This off-path signaling can be as simple as a DNS query, link-level broadcast, or a more complicated SIP discovery/negotiation. -- Some lookup mechanism that _won't_ be used for the actual data. If N and M are firewall/NAT boxes, they need not be explicitly addressed, therefore there is no such need for an off-path lookup to discover N/M -- i.e. N and M can be discovered (invoked?) by the same mechanism that'll be used to send data (unicast IP routing from A to B). An off-path lookup, however, may still be needed to find B in the first place. Not sure if I answered your question, -- Saikat
_______________________________________________ OFF-PATH-BOF mailing list OFF-PATH-BOF@ietf.org https://www1.ietf.org/mailman/listinfo/off-path-bof
- Re: [OFF-PATH-BOF] SIP, naming, APIs and control Melinda Shore
- Re: [OFF-PATH-BOF] SIP, naming, APIs and control Saikat Guha
- [OFF-PATH-BOF] SIP, naming, APIs and control Teemu Koponen
- Re: [OFF-PATH-BOF] SIP, naming, APIs and control Melinda Shore
- Re: [OFF-PATH-BOF] SIP, naming, APIs and control Teemu Koponen
- Re: [OFF-PATH-BOF] SIP, naming, APIs and control Teemu Koponen
- Re: [OFF-PATH-BOF] SIP, naming, APIs and control Saikat Guha
- Re: [OFF-PATH-BOF] SIP, naming, APIs and control Saikat Guha
- [OFF-PATH-BOF] Proposed IRTF agenda Paul Francis
- Re: [OFF-PATH-BOF] SIP, naming, APIs and control Scott W Brim
- Re: [OFF-PATH-BOF] SIP, naming, APIs and control Saikat Guha
- [OFF-PATH-BOF] Proposed IRTF agenda Paul Francis