---

---

en.wordpress.com/tag/how-many-shares-does-dorota-get-hello-employee-stock-options

---

Posted by crouse

Option tags are unique identifiers used to designate new options in SIP. These tags are used in
Require (Section 6.30) and Unsupported (Section 6.38) fields.

Syntax:

option-tag = token

See Section C for a definition of token. The creator of a new SIP option MUST either prefix the option with their reverse domain name or register the new option with the Internet Assigned Numbers Authority (IANA). For example, "com.foo.mynewfeature" is an apt name for a feature whose inventor can be reached at "foo.com". Individual organizations are then responsible for ensuring that option names don't collide. Options registered with IANA have the prefix "org.iana.sip.", options described in RFCs have the prefix "org.ietf.rfc.N", where N is the RFC number. Option tags are case-insensitive.

---

Posted by snjysanjay05

Option tags are used in header fields such as Require,
Supported, Proxy-Require, and Unsupported in support of
SIP compatibility mechanisms for extensions. The option
tag itself is a string that is associated with a particular
SIP option (that is, an extension).
It identifies the option to SIP endpoints.

---

Posted by sagitraz