[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 5.1) SSH End of message directive


There are a couple of reasons why <?Netconf-EOM?> may
be a better choice than just <?eom?>.  One would be that
any future Netconf PI's would always begin with
"<?Netconf-", not too unlike PI's with 'xml' are reserved
by XML 1.0.

Another reason why <?Netconf-EMS?> may be better than just
<?eom?> is that tunneling XML constructs inside of other
XML constructs for more sophisticated network management
infrastructure is possible, and if someone wishes to
embed a sequence of messages to send down to an NE which
is tunneled, the <?Netconf-EMS?> PI would be a bit more
tricky to confuse with other <?eom?> which may be present
for perhaps non-Netconf reasons.  Perhaps unlikely, but an
ounce of prevention...

Juergen,

I agree with your CDATA scenario and I am open to suggestions for something
kind of illegal.

Tim

-----Original Message-----
From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de]
Sent: Thursday, February 19, 2004 3:01 PM
To: tstoddar@utstar.com
Cc: netconf@ops.ietf.org
Subject: Re: Issue 5.1) SSH End of message directive




Tim Stoddard writes: 


Tim> To a single parser I concede there is no difference between
Tim> <?EOM?> and <?Netconf_EOM?>, however if there are cases where
Tim> other delimiters are involved in the framing I think <?EOM?> is
Tim> quite generic and a way to alleviate that situation is to be
Tim> specific with the <?Netconf_EOM?> delimiter.

Not sure I see this problem. The sending netconf engine inserts
<?EOM?> at the end of a netconf message and the receiving engine
eats the <?EOM?> to separate out the message again. This is the
netconf framing - so in which situation should there be another
framing that causes problems?

The only realisitc issue I see is that some netconf messages might
contain <?EOM?> in a CDATA portion of the payload. So if we look for a
better <?EOM?>, than it should be something that is kind of illegal in
XML, regardless where it appears in an XML document. Not sure this
exists (probably requires some careful study of the XML specs), but
this would for me be a real improvement.

/js

--
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany



--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>



--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>