Name,Description,Reference
100rel,"This option tag is for reliability of
provisional responses. When present in a
Supported header, it indicates that the UA
can send or receive reliable provisional
responses. When present in a Require header
in a request it indicates that the UAS MUST
send all provisional responses reliably.
When present in a Require header in a
reliable provisional response, it indicates
that the response is to be sent reliably.",[RFC3262]
199,"This option-tag is for indicating support
of the 199 Early Dialog Terminated
provisional response code. When present in a
Supported header of a request, it indicates
that the UAC supports the 199 response code.
When present in a Require or Proxy-Require
header field of a request, it indicates that
the UAS, or proxies, MUST support the 199
response code. It does not require the UAS,
or proxies, to actually send 199 responses.",[RFC6228]
answermode,"This option tag is for support of the
Answer-Mode and Priv-Answer-Mode
extensions used to negotiate automatic
or manual answering of a request.",[RFC5373]
early-session,"A UA adding the early-session option tag
to a message indicates that it understands
the early-session content disposition.",[RFC3959]
eventlist,"Extension to allow subscriptions to lists
of resources",[RFC4662]
explicitsub,"This option tag identifies an extension to REFER to
suppress the implicit subscription and provide a URI for an explicit
subscription.",[RFC7614]
from-change,"This option tag is used to indicate that
a UA supports changes to URIs in From and
To header fields during a dialog.",[RFC4916]
geolocation-http,"The ""geolocation-http"" option tag signals support for acquiring location information
via an HTTP [RFC2616]. A location
recipient who supports this option can
request location with an HTTP GET and
parse a resulting 200 response containing
a PIDF-LO object. The URI schemes
supported by this option include ""http""
and ""https"".",[RFC6442]
geolocation-sip,"The ""geolocation-sip"" option tag signals
support for acquiring location information
via the presence event package of SIP
[RFC3856]. A location recipient who
supports this option can send a SUBSCRIBE
request and parse a resulting NOTIFY
containing a PIDF-LO object. The URI
schemes supported by this option include
""sip"", ""sips"", and ""pres"".",[RFC6442]
gin,"This option tag is used to identify the
extension that provides Registration for
Multiple Phone Numbers in SIP. When present
in a Require or Proxy-Require header field of
a REGISTER request, it indicates that support
for this extension is required of registrars
and proxies, respectively, that are a party
to the registration transaction.",[RFC6140]
gruu,"This option tag is used to identify the Globally
Routable User Agent URI (GRUU) extension. When
used in a Supported header, it indicates that
a User Agent understands the extension.
When used in a Require header field of a REGISTER
request, it indicates that the registrar is
not expected to process the registration unless
it supports the GRUU extension.",[RFC5627]
histinfo,"When used with the Supported header
field, this option tag indicates the UAC
supports the History Information to be
captured for requests and returned in
subsequent responses. This tag is not
used in a Proxy-Require or Require
header field, since support of
History-Info is optional.",[RFC7044]
ice,"This option tag is used to identify the
Interactive Connectivity Establishment (ICE)
extension. When present in a Require header
field, it indicates that ICE is required by
an agent.",[RFC5768]
join,Support for the SIP Join Header,[RFC3911]
multiple-refer,"This option tag indicates support
for REFER requests that contain a
resource list document describing
multiple REFER targets.",[RFC5368]
norefersub,"This option tag specifies a User Agent
ability of accepting a REFER request without
establishing an implicit subscription
(compared to the default case defined in
[RFC3515].",[RFC4488]
nosub,"This option tag identifies an extension to REFER to
suppress the implicit subscription and indicate that no explicit
subscription is forthcoming.",[RFC7614]
outbound,"This option-tag is used to identify UAs and
Registrars which support extensions for
Client Initiated Connections. A UA places
this option in a Supported header to
communicate its support for this extension.
A Registrar places this option-tag in a
Require header to indicate to the
registering User Agent that the Registrar
used registrations using the binding rules
defined in this extension.",[RFC5626]
path,"A SIP UA that supports the Path extension
header field includes this option tag as a
header field value in a Supported header
field in all requests generated by that UA.
Intermediate proxies may use the presence
of this option tag in a REGISTER request to
determine whether to offer Path service for
for that request. If an intermediate proxy
requires that the registrar support Path for
a request, then it includes this option tag
as a header field value in a Requires
header field in that request.",[RFC3327]
policy,"This option tag is used to indicate that
a UA can process policy server URIs for
and subscribe to session-specific
policies.",[RFC6794]
precondition,"An offerer MUST include this tag in the
Require header field if the offer contains
one or more ""mandatory"" strength-tags. If
all the strength-tags in the description are
""optional"" or ""none"" the offerer MUST include
this tag either in a Supported header field
or in a Require header field.",[RFC3312]
pref,"This option tag is used to ensure that a
server understands the callee capabilities
parameters used in the request.",[RFC3840]
privacy,"This option tag indicates support for the
Privacy mechanism. When used in the
Proxy-Require header, it indicates that proxy
servers do not forward the request unless they
can provide the requested privacy service.
This tag is not used in the Require or
Supported headers. Proxies remove this option
tag before forwarding the request if the desired
privacy function has been performed.",[RFC3323]
recipient-list-invite,"The body contains a list of URIs that indicates the recipients of the
SIP INVITE request",[RFC5366]
recipient-list-message,"The body contains a list of URIs that indicates the recipients of
the SIP MESSAGE request",[RFC5365]
recipient-list-subscribe,"This option tag is used to ensure that a server can process the
recipient-list body used in a
SUBSCRIBE request.",[RFC5367]
record-aware,"This option tag is to indicate the ability of the UA to
receive recording indicators in media-level or session-level SDP.
When present in a Supported header, it indicates that the UA can
receive recording indicators in media-level or session-level SDP.",[RFC7866]
replaces,"This option tag indicates support for the
SIP Replaces header.",[RFC3891]
resource-priority,Indicates or requests support for the resource priority mechanism.,[RFC4412]
sdp-anat,"The option-tag sdp-anat is defined for use
in the Require and Supported SIP [RFC3261]
header fields. SIP user agents that place this
option-tag in a Supported header field understand
the ANAT semantics as defined in [RFC4091].",[RFC4092]
sec-agree,"This option tag indicates support for the
Security Agreement mechanism. When used in the
Require, or Proxy-Require headers, it indicates
that proxy servers are required to use the
Security Agreement mechanism. When used in
the Supported header, it indicates that the
User Agent Client supports the Security Agreement
mechanism. When used in the Require header
in the 494 (Security Agreement Required) or
421 (Extension Required) responses, it
indicates that the User Agent Client must
use the Security Agreement Mechanism.",[RFC3329]
siprec,"This option tag is for identifying that the SIP
session is for the purpose of an RS. This is
typically not used in a Supported header. When present in a
Require header in a request, it indicates that the UA is either an
SRC or SRS capable of handling a recording session.",[RFC7866]
tdialog,"This option tag is used to identify the target
dialog header field extension. When used in
a Require header field, it implies that the
recipient needs to support the Target-Dialog
header field. When used in a Supported header
field, it implies that the sender of the message
supports it.",[RFC4538]
timer,"This option tag is for support of the
session timer extension. Inclusion in a Supported
header field in a request or response indicates
that the UA is capable of performing refreshes
according to that specification. Inclusion
in a Require header in a request means that
the UAS must understand the session timer extension
to process the request. Inclusion in a Require
header field in a response indicates that the
UAC must look for the Session-Expires header
field in the response, and process accordingly.",[RFC4028]
trickle-ice,This option tag is used to indicate that a UA supports and understands Trickle ICE.,[RFC8840]
uui,"This option tag is used to indicate that
a UA supports and understands the User-to-User header field.",[RFC7433]
Presently we were in a very dark road, and at a point where it dropped suddenly between steep sides we halted in black shadow. A gleam of pale sand, a whisper of deep flowing waters, and a farther glimmer of more sands beyond them challenged our advance. We had come to a "grapevine ferry." The scow was on the other side, the water too shoal for the horses to swim, and the bottom, most likely, quicksand. Out of the blackness of the opposite shore came a soft, high-pitched, quavering, long-drawn, smothered moan of woe, the call of that snivelling little sinner the screech-owl. Ferry murmured to me to answer it and I sent the same faint horror-stricken tremolo back. Again it came to us, from not farther than one might toss his cap, and I followed Ferry down to the water's edge. The grapevine guy swayed at our side, we heard the scow slide from the sands, and in a few moments, moved by two videttes, it touched our shore. Soon we were across, the two videttes riding with us, and beyond a sharp rise, in an old opening made by the swoop of a hurricane, we entered the silent unlighted bivouac of Ferry's scouts. Ferry got down and sat on the earth talking with Quinn, while the sergeants quietly roused the sleepers to horse. Plotinus is driven by this perplexity to reconsider the whole theory of Matter.477 He takes Aristotle¡¯s doctrine as the groundwork of his investigation. According to this, all existence is divided into Matter and Form. What we know of things¡ªin other words, the sum of their differential characteristics¡ªis their Form. Take away this, and the unknowable residuum is their Matter. Again, Matter is the vague indeterminate something out of which particular Forms are developed. The two are related as Possibility to Actuality, as the more generic to the more specific substance through every grade of classification and composition. Thus there are two Matters, the one sensible and the other intelligible. The former constitutes the common substratum of bodies, the other the common element of ideas.478 The general distinction between Matter and Form was originally suggested to Aristotle by Plato¡¯s remarks on the same subject; but he differs325 from his master in two important particulars. Plato, in his Timaeus, seems to identify Matter with space.479 So far, it is a much more positive conception than the ?λη of the Metaphysics. On the other hand, he constantly opposes it to reality as something non-existent; and he at least implies that it is opposed to absolute good as a principle of absolute evil.480 Thus while the Aristotelian world is formed by the development of Power into Actuality, the Platonic world is composed by the union of Being and not-Being, of the Same and the Different, of the One and the Many, of the Limit and the Unlimited, of Good and Evil, in varying proportions with each other. The Lawton woman had heard of an officer's family at Grant, which was in need of a cook, and had gone there. [See larger version] On the 8th of July an extraordinary Privy Council was summoned. All the members, of whatever party, were desired to attend, and many were the speculations as to the object of their meeting. The general notion was that it involved the continuing or the ending of the war. It turned out to be for the announcement of the king's intended marriage. The lady selected was Charlotte, the second sister of the Duke of Mecklenburg-Strelitz. Apart from the narrowness of her education, the young princess had a considerable amount of amiability, good sense, and domestic taste. These she shared with her intended husband, and whilst they made the royal couple always retiring, at the same time they caused them to give, during their lives, a moral air to their court. On the 8th of September Charlotte arrived at St. James's, and that afternoon the marriage took place, the ceremony being performed by the Archbishop of Canterbury. On the 22nd the coronation took place with the greatest splendour. Mother and girls were inconsolable, for each had something that they were sure "Si would like," and would "do him good," but they knew Josiah Klegg, Sr., well enough to understand what was the condition when he had once made up his mind. CHAPTER V. THE YOUNG RECRUITS Si proceeded to deftly construct a litter out of the two guns, with some sticks that he cut with a knife, and bound with pawpaw strips. His voice had sunk very low, almost to sweetness. A soft flurry of pink went over her face, and her eyelids drooped. Then suddenly she braced herself, pulled herself taut, grew combative again, though her voice shook. HoME²Ô¾®Ïè̫ʲôÐÇ×ù
ENTER NUMBET 0016www.kfgowt.com.cn
www.qiang1122.net.cn
www.wanzitv.com.cn
www.mmshop.net.cn
www.pyszro.com.cn
www.qnjswp.com.cn
rfbboo.com.cn
tyqbke.com.cn
www.obsmo.com.cn
www.rlxeyt.com.cn