[OFF-PATH-BOF] SIP, naming, APIs and control

Teemu Koponen <koponen@ICSI.Berkeley.EDU> Thu, 13 July 2006 17:35 UTC

Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G155j-0003Xl-9t; Thu, 13 Jul 2006 13:35:11 -0400
Received: from [] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G155i-0003XX-I1 for off-path-bof@ietf.org; Thu, 13 Jul 2006 13:35:10 -0400
Received: from nz-out-0102.google.com ([]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G155g-0000Rm-8v for off-path-bof@ietf.org; Thu, 13 Jul 2006 13:35:10 -0400
Received: by nz-out-0102.google.com with SMTP id i11so8742nzi for <off-path-bof@ietf.org>; Thu, 13 Jul 2006 10:35:08 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:content-transfer-encoding:message-id:content-type:to:from:subject:date:x-mailer:sender; b=l7VxsLHubTi2VRFB+MsK9R2vFLrHqV4JYSB2e9yfWIgSMGDvty9Me8MS7ouUvxI0d4YqRw+1hmqrwpz4wT8Lkh2UWb0PngNuoUptQ1fl8QzRDvCtkqBzyG1zYPVPZRZSU6FW4/mEBxxnWA3jqde1SqcymHm5j6XPT7A/onYX/c8=
Received: by with SMTP id v20mr354598qbl; Thu, 13 Jul 2006 10:35:07 -0700 (PDT)
Received: from ? ( []) by mx.gmail.com with ESMTP id q16sm1285165qbq.2006.; Thu, 13 Jul 2006 10:35:07 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <CA038C2C-5AD9-440E-889D-F86FBE678B55@ICSI.Berkeley.EDU>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: off-path-bof@ietf.org
From: Teemu Koponen <koponen@ICSI.Berkeley.EDU>
Date: Thu, 13 Jul 2006 10:35:02 -0700
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Subject: [OFF-PATH-BOF] SIP, naming, APIs and control
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>
Errors-To: off-path-bof-bounces@ietf.org

Thanks for a very interesting BoF, Paul, Mark and Saikat.  There's
definitely ongoing work in this area elsewhere too. :) Here's my
unstructured initial stake on the matter.

I have to say that I was more than slightly concerned about the
proposed content before hearing the presentations. It seemed that the
called approach would not be a "clean-slate" one but a more
engineering oriented effort. Especially,

o) The promotion of SIP was concerning. I tend to see the current SIP
as a rather complex beast indeed. While it does have certain
attractive primitives built-in (e.g., delegation to impose off-path
middleboxes), I would not like to remain fixed to SIP. In the end, I
believe something more simple can meet the requirements. Fortunately,
SIP was less emphasized in the presentions themselves than in the

o) Mixing the needs to persistently identify an end-point for machines
and for users was distracting.  I do not think hierarchical names
should remain the sole option to consider. Flat names are rather
attractive option indeed to identify end-points for machines. In fact,
I think one should support both.

"Newsock" was mentioned, but I was somewhat confused when the focus
was in the API and when in the protocol.  I feel that explicitly
considering the API first would enforce us to think the requirements
before moving down to the protocol level issues. Moreover, I could
imagine an outcome where applications could use multiple "offpath
protocols" through the same API.

The fundamental aspect I still do not understand is that how the
decoupling of signaling and data paths helps at all. It strikes to be
problem roaming only for me. (I think Bob Briscoe asked this without
getting a decent answer.) I'm not sure whether I heard the word in
some comment, but I think the group name misses a single word:
control. This all is about getting the control back to the end-points
and not that much about decoupling the paths.



OFF-PATH-BOF mailing list