IETF Logo Mail Archive

Re: [Spud] FW: New Version Notification for draft-hildebrand-spud-prototype-02.txt

Ken Calvert <calvert@netlab.uky.edu> Fri, 06 March 2015 21:46 UTC

Return-Path: <calvert@netlab.uky.edu>
X-Original-To: spud@ietfa.amsl.com
Delivered-To: spud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 255041A1A8B for <spud@ietfa.amsl.com>; Fri, 6 Mar 2015 13:46:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.289
X-Spam-Level:
X-Spam-Status: No, score=0.289 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_ALL=0.8, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ABoonK7U4rdV for <spud@ietfa.amsl.com>; Fri, 6 Mar 2015 13:46:04 -0800 (PST)
Received: from mail3.netlab.uky.edu (wonder.netlab.uky.edu [128.163.140.37]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B42161A0100 for <spud@ietf.org>; Fri, 6 Mar 2015 13:46:04 -0800 (PST)
Received: from culp.local (cpe-96-29-241-159.swo.res.rr.com [96.29.241.159]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail3.netlab.uky.edu (Postfix) with ESMTPSA id 27AACC103; Fri, 6 Mar 2015 16:46:02 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_26640739-6728-4804-9279-A7983BA5890F"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ken Calvert <calvert@netlab.uky.edu>
In-Reply-To: <CAOdDvNrRcMCnWMzBvL0Do16mmiajeR4OJRx36cxnppuaD7+81w@mail.gmail.com>
Date: Fri, 06 Mar 2015 16:46:00 -0500
Message-Id: <F1A52CC0-299E-465F-BCA2-A4D4F3DEA6A4@netlab.uky.edu>
References: <20150303155825.32731.37010.idtracker@ietfa.amsl.com> <08728A73-ED15-4928-A5BB-A59EA9E6D785@cisco.com> <CA+9kkMDSMMUByAMOc8gSyMajyKj0ZtZzmFPg+J7bz-6AYkFYhw@mail.gmail.com> <CAOdDvNrRcMCnWMzBvL0Do16mmiajeR4OJRx36cxnppuaD7+81w@mail.gmail.com>
To: Patrick McManus <mcmanus@ducksong.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/AejpJCxhaiR2_K1h1SDdxDzrMxs>
Cc: "spud@ietf.org" <spud@ietf.org>
Subject: Re: [Spud] FW: New Version Notification for draft-hildebrand-spud-prototype-02.txt
X-BeenThere: spud@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Session Protocol Underneath Datagrams <spud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spud>, <mailto:spud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spud/>
List-Post: <mailto:spud@ietf.org>
List-Help: <mailto:spud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spud>, <mailto:spud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2015 21:46:06 -0000

On 6 Mar 2015, at 15:52, Patrick McManus <mcmanus@ducksong.com> wrote:

> Next, I may just be confused because I have read the text less than the authors at this point, but it seems as if unidirectional flows are off the table.. the text doesn't really say this, but the open-ack seems to imply it. There certainly are unidirectional udp flows but some clarification would help.

Actually, the state machine diagram - which I interpreted as applying at ANY specific point along a path - doesn't (quite) imply the above, at least as I interpret it.  It seems to work fine for a middlebox that only sees the initiator->responder side (i.e., the only side of a unidirectional flow).  Although in that case it looks like the initiator doesn't get out of "resuming" state...

> ...

> Fourthly, there are a couple "reserved bits MUST be zero".. should that be "senders MUST set to zero, receivers MUST ignore "?

Along those lines, it seems the intent is that ONLY endpoints touch the "command" bits, and that middleboxes MUST NOT modify them.  (SHOULD NOT?  Are there non-nefarious use cases?)  This should probably be made explicit; I didn't see it anywhere, sorry if I missed it.

Ken Calvert

v2.23.0 | Report a Bug | By Email