[DNSOP] draft-ietf-dnsop-session-signal: session establishment

["Paul Hoffman" <[e-mail]>]

Greetings. The -05 draft still has a complexity that I can can be easily 
fixed. In a few places, it says that a session can be established by the 
client sending a response-requiring DSO request message. For example, 
from section 4.1:
    A DSO Session is established over a connection by the client sending
    a DSO request message of a kind that requires a response, such as 
the
    DSO Keepalive TLV (see Section 6.1), and receiving a response, with
    matching MESSAGE ID, and RCODE set to NOERROR (0), indicating that
    the DSO request was successful.

This logic requires a client to survey all the kinds of requests it 
knows to find one appropriate for establishing the session. It also 
requires the server to have to check the first message for any kind of 
response-requiring request message.

Why not just say that the session MUST be established by the client 
sending a Keepalive message? That message must be understood by all 
parties, and both the values in it have defaults listed in the draft. A 
client who has not real preference for the inactivity timeout or 
keepalive interval can just use the defaults; a client with a stronger 
opinion can start the session with what it wants.

This change would simplify the draft in a bunch of places by making the 
protocol more definitive.

--Paul Hoffman