rfc3840 contains the phrase "whether the UA represents an automata".

Leaving aside the question of whether you say tomato and I say tomayto,
"automata" is of course plural so this phrase is ungrammatical - the
singular is of course "automaton" - perhaps this is where the confusion
started.

More generally, I am do find very interestng the question of how
complete and formal these standards should be. Clearly some of these
documents were written at a time when the breath-taking scale and
scope of their application was unknown and time was of the essence.
A "loose" specification can leave room for further development e.g.
standard plus profile, and this doesn't need to be imprecise. But I
wonder how much the lack of formality and formal review has contributed
to error and flakiness.

Cheers,

Tom Lake

-------------------------------------------------------------------------
  Tom Lake   Interglossa Ltd        |   SnailPhone: 0118 926 2896       |
  email: [email protected]      |   SnailMail: Interglossa Ltd      |
  mob: 079 638 15599                |      59, Alexandra Road           |
  web:  glossa.co.uk                |      Reading RG1 5PG              |
  twitter: @TomWLake                |      UK                           |
 ------------------------------------------------------------------------

On Tue, 29 Apr 2014, Paul Kyzivat wrote:

I presume "automaton" is simply an error - a misspelling.
You can look in the iana registry for all the defined feature tags.

On 4/29/14 3:27 AM, SIP Learner wrote:
 Hi, guys!


 I am reading RFC5359 for SIP services examples, some of the message
 examples contain a Contact header parameter like the following:


 Contact: <sips:[email protected]>;automaton
 ;+sip.byeless;+sip.rendering="no"



 FRC5359 states that the automaton feature tag is defined in RFC3840, but
 RFC3840 actually defined sip.automata instead of automaon.


 What is the difference between automaton and sip.automata anyway? Are they
 equivalent or are they different?


 Thanks a lot!
 _______________________________________________
 Sip-implementors mailing list
 [email protected]
 https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors


_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors


_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to