[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: message-id attribute issues
On Tue, Dec 20, 2005 at 02:37:05AM -0800, Andy Bierman wrote:
> >CLR? ;-) Seriously, I think implementors may find creative things
> >to do with message-id, and 255 could be a bit short. Every
> >implementation
> >will have a practical limit on the messages that can be received; do you
> >think we should limit it in the spec?
>
> Right now we have a limit -- it's 65535.
> If your agent doesn't accept a message-id attribute this big, it is broken.
>
> (Imagine that some company like IWL is going to write a test suite
> to test every one of these limits and tell your customers every place your
> agent is broken.)
What about distinguishing between the upper limits as expressed in the
XSD and implementation "conformance" requirements? I believe
xsd:string is just fine wrt. the upper limit. If people feel strongly
that there should be a smaller minimum implementation requirement,
then lets define these things as part of an applicability statement or
as implementation guidelines. The point is to not hardwire arbitrary
choices if we do not have to.
/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/>