mailbox403forbidden
403forbidden 时间:2021-04-12 阅读:()
NetworkWorkingGroupA.
B.
RoachRequestforComments:3265dynamicsoftCategory:StandardsTrackJune2002Updates:2543SessionInitiationProtocol(SIP)-SpecicEventNoticationStatusofthisMemoThisdocumentspeciesanInternetstandardstrackprotocolfortheInternetcommunity,andrequestsdiscus-sionandsuggestionsforimprovements.
Pleaserefertothecurrenteditionofthe"InternetOfcialProtocolStandards"(STD1)forthestandardizationstateandstatusofthisprotocol.
Distributionofthismemoisunlimited.
CopyrightNoticeCopyright(c)TheInternetSociety(2002).
AllRightsReserved.
AbstractThisdocumentdescribesanextensiontotheSessionInitiationProtocol(SIP).
ThepurposeofthisextensionistoprovideanextensibleframeworkbywhichSIPnodescanrequestnoticationfromremotenodesindicatingthatcertaineventshaveoccurred.
Concreteusesofthemechanismdescribedinthisdocumentmaybestandardizedinthefuture.
NotethattheeventnoticationmechanismsdenedhereinareNOTintendedtobeageneral-purposeinfrastructureforallclassesofeventsubscriptionandnotication.
Contents1Introduction31.
1OverviewofOperation41.
2DocumentationConventions42Denitions53NodeBehavior53.
1DescriptionofSUBSCRIBEBehavior53.
1.
1SubscriptionDuration63.
1.
2IdenticationofSubscribedEventsandEventClasses63.
1.
3AdditionalSUBSCRIBEHeaderValues73.
1.
4SubscriberSUBSCRIBEBehavior73.
1.
5ProxySUBSCRIBEBehavior8RFC3265SIP-SpecicEventNoticationJune20023.
1.
6NotierSUBSCRIBEBehavior83.
2DescriptionofNOTIFYBehavior103.
2.
1IdenticationofReportedEvents,EventClasses,andCurrentState113.
2.
2NotierNOTIFYBehavior113.
2.
3ProxyNOTIFYBehavior123.
2.
4SubscriberNOTIFYBehavior123.
3General143.
3.
1DetectingsupportforSUBSCRIBEandNOTIFY143.
3.
2CANCELrequests143.
3.
3Forking143.
3.
4Dialogcreationandtermination143.
3.
5StateAgentsandNotierMigration153.
3.
6PollingResourceState153.
3.
7Allow-Eventsheaderusage163.
3.
8PINTCompatibility164EventPackages164.
1AppropriatenessofUsage164.
2EventTemplate-packages174.
3AmountofStatetobeConveyed174.
3.
1CompleteStateInformation174.
3.
2StateDeltas184.
4EventPackageResponsibilities184.
4.
1EventPackageName184.
4.
2EventPackageParameters184.
4.
3SUBSCRIBEBodies184.
4.
4SubscriptionDuration194.
4.
5NOTIFYBodies194.
4.
6NotierprocessingofSUBSCRIBErequests194.
4.
7NotiergenerationofNOTIFYrequests194.
4.
8SubscriberprocessingofNOTIFYrequests194.
4.
9Handlingofforkedrequests204.
4.
10Rateofnotications204.
4.
11StateAgents204.
4.
12Examples204.
4.
13UseofURIstoRetrieveState21RoachStandardsTrack[Page2]RFC3265SIP-SpecicEventNoticationJune20025SecurityConsiderations215.
1AccessControl215.
2NotierPrivacyMechanism215.
3Denial-of-Serviceattacks215.
4ReplayAttacks225.
5Man-in-themiddleattacks225.
6Condentiality226IANAConsiderations226.
1RegistrationInformation237RegistrationTemplate237.
1HeaderFieldNames247.
2ResponseCodes248Syntax258.
1NewMethods258.
1.
1SUBSCRIBEmethod268.
1.
2NOTIFYmethod268.
2NewHeaders278.
2.
1Eventheader278.
2.
2Allow-EventsHeader278.
2.
3Subscription-StateHeader278.
3NewResponseCodes288.
3.
1"202Accepted"ResponseCode288.
3.
2"489BadEvent"ResponseCode288.
4AugmentedBNFDenitions289Acknowledgements2910NoticeRegardingIntellectualPropertyRights3011Author'sAddress301IntroductionTheabilitytorequestasynchronousnoticationofeventsprovesusefulinmanytypesofSIPservicesforwhichcooperationbetweenend-nodesisrequired.
ExamplesofsuchservicesincludeautomaticcallbackRoachStandardsTrack[Page3]RFC3265SIP-SpecicEventNoticationJune2002services(basedonterminalstateevents),buddylists(basedonuserpresenceevents),messagewaitingindications(basedonmailboxstatechangeevents),andPSTNandInternetInternetworking(PINT)[1]status(basedoncallstateevents).
Themethodsdescribedinthisdocumentprovideaframeworkbywhichnoticationoftheseeventscanbeordered.
TheeventnoticationmechanismsdenedhereinareNOTintendedtobeageneral-purposeinfrastructureforallclassesofeventsubscriptionandnotication.
Meetingrequirementsforthegeneralproblemsetofsubscriptionandnoticationisfartoocomplexforasingleprotocol.
OurgoalistoprovideaSIP-specicframeworkforeventnoticationwhichisnotsocomplexastobeunusableforsimplefeatures,butwhichisstillexibleenoughtoprovidepowerfulservices.
Note,however,thateventpackagesbasedonthisframeworkmaydenearbitrarilyelaborateruleswhichgovernthesubscriptionandnoticationfortheeventsorclassesofeventstheydescribe.
Thisdocumentdoesnotdescribeanextensionwhichmaybeuseddirectly;itmustbeextendedbyotherdoc-uments(hereinreferredtoas"eventpackages").
Inobject-orienteddesignterminology,itmaybethoughtofasanabstractbaseclasswhichmustbederivedintoaninstantiatableclassbyfurtherextensions.
Guidelinesforcreatingtheseextensionsaredescribedinsection4.
1.
1OverviewofOperationThegeneralconceptisthatentitiesinthenetworkcansubscribetoresourceorcallstateforvariousresourcesorcallsinthenetwork,andthoseentities(orentitiesactingontheirbehalf)cansendnoticationswhenthosestateschange.
Atypicalowofmessageswouldbe:SubscriberNotifier|-----SUBSCRIBE---->|Requeststatesubscription200-Acknowledgesubscription|REFERENCES[RFC3265]Roach,A.
,"SIP-SpecificEventNotification",RFC3265,June2002.
7RegistrationTemplateTo:ietf-sip-events@iana.
orgSubject:RegistrationofnewSIPeventpackageRoachStandardsTrack[Page23]RFC3265SIP-SpecicEventNoticationJune2002PackageName:(Packagenamesmustconformtothesyntaxdescribedinsection\ref{sec:Event}.
)IsthisregistrationforaTemplatePackage:(indicateyesorno)PublishedSpecification(s):(TemplatepackagesrequireapublishedRFC.
Otherpackagesmayreferenceaspecificationwhenappropriate).
Person&emailaddresstocontactforfurtherinformation:7.
1HeaderFieldNamesThisdocumentregistersthreenewheadereldnames,describedelsewhereinthisdocument.
Theseheadersaredenedbythefollowinginformation,whichistobeaddedtotheheadersub-registryunderhttp://www.
iana.
org/aHeaderName:Allow-EventsCompactForm:uHeaderName:Subscription-StateCompactForm:(none)HeaderName:EventCompactForm:o7.
2ResponseCodesThisdocumentregisterstwonewresponsecodes.
Theseresponsecodesaredenedbythefollowinginfor-mation,whichistobeaddedtothemethodandresponse-codesub-registryunderhttp://www.
iana.
org/assignmentResponseCodeNumber:202DefaultReasonPhrase:AcceptedResponseCodeNumber:489DefaultReasonPhrase:BadEventRoachStandardsTrack[Page24]RFC3265SIP-SpecicEventNoticationJune20028SyntaxThissectiondescribesthesyntaxextensionsrequiredforeventnoticationinSIP.
Semanticsaredescribedinsection3.
NotethattheformalsyntaxdenitionsdescribedinthisdocumentareexpressedintheABNFformatusedinSIP[2],andcontainreferencestoelementsdenedtherein.
8.
1NewMethodsThisdocumentdescribestwonewSIPmethods:SUBSCRIBEandNOTIFY.
Thistableexpandsontables2and3inSIP[2].
HeaderWhereSUBNOTAcceptRooAccept2xx--Accept415ooAccept-EncodingRooAccept-Encoding2xx--Accept-Encoding415ooAccept-LanguageRooAccept-Language2xx--Accept-Language415ooAlert-InfoR--Alert-Info180--AllowRooAllow2xxooAllowrooAllow405mmAuthentication-Info2xxooAuthorizationRooCall-IDcmmContactRmmContact1xxooContact2xxmoContact3xxmmContact485ooContent-DispositionooContent-EncodingooContent-LanguageooContent-LengthttContent-Type**CSeqcmmDateooError-Info300-699ooRoachStandardsTrack[Page25]RFC3265SIP-SpecicEventNoticationJune2002Expireso-Expires2xxm-FromcmmIn-Reply-ToR--Max-ForwardsRmmMin-Expires423m-MIME-VersionooOrganizationo-PriorityRo-Proxy-Authenticate407mmProxy-AuthorizationRooProxy-RequireRooRAckR--Record-RouteRooRecord-Route2xx,401,484ooReply-To--RequireooRetry-After404,413,480,486ooRetry-After500,503ooRetry-After600,603ooRouteRccRSeq1xxooServerrooSubjectR--SupportedRooSupported2xxooTimestampooToc(1)mmUnsupported420ooUser-AgentooViacmmWarningR-oWarningrooWWW-Authenticate401mm8.
1.
1SUBSCRIBEmethodSUBSCRIBEisaddedtothedenitionoftheelementMethodintheSIPmessagegrammar.
LikeallSIPmethodnames,theSUBSCRIBEmethodnameiscasesensitive.
TheSUBSCRIBEmethodisusedtorequestasynchronousnoticationofaneventorsetofeventsatalatertime.
8.
1.
2NOTIFYmethodNOTIFYisaddedtothedenitionoftheelementMethodintheSIPmessagegrammar.
RoachStandardsTrack[Page26]RFC3265SIP-SpecicEventNoticationJune2002TheNOTIFYmethodisusedtonotifyaSIPnodethataneventwhichhasbeenrequestedbyanearlierSUBSCRIBEmethodhasoccurred.
Itmayalsoprovidefurtherdetailsabouttheevent.
8.
2NewHeadersThistableexpandsontables2and3inSIP[2],asamendedbythechangesdescribedinsection8.
1.
HeaderfieldwhereproxyACKBYECANINVOPTREGPRASUBNOTAllow-EventsRoo-ooooooAllow-Events2xx-o-ooooooAllow-Events489mmEventRmmSubscription-StateRm8.
2.
1EventheaderEventisaddedtothedenitionoftheelementmessage-headerintheSIPmessagegrammar.
ForthepurposesofmatchingresponsesandNOTIFYmessageswithSUBSCRIBEmessages,theevent-typeportionoftheEventheaderiscomparedbyte-by-byte,andtheidparametertoken(ifpresent)iscom-paredbyte-by-byte.
AnEventheadercontaininganidparameternevermatchesanEventheaderwithoutanidparameter.
Nootherparametersareconsideredwhenperformingacomparison.
Notethattheforgoingtextmeansthat"Event:foo;id=1234"wouldmatch"Event:foo;param=abcd;id=1234",butnot"Event:foo"(iddoesnotmatch)or"Event:Foo;id=1234"(eventportiondoesnotmatch).
Thisdocumentdoesnotdenevaluesforevent-types.
Thesevalueswillbedenedbyindividualeventpackages,andMUSTberegisteredwiththeIANA.
ThereMUSTbeexactlyoneeventtypelistedpereventheader.
Multipleeventspermessagearedisallowed.
8.
2.
2Allow-EventsHeaderAllow-Eventsisaddedtothedenitionoftheelementgeneral-headerintheSIPmessagegrammar.
Itsusageisdescribedinsection3.
3.
7.
8.
2.
3Subscription-StateHeaderSubscription-Stateisaddedtothedenitionoftheelementrequest-headerintheSIPmessagegrammar.
Itsusageisdescribedinsection3.
2.
4.
RoachStandardsTrack[Page27]RFC3265SIP-SpecicEventNoticationJune20028.
3NewResponseCodes8.
3.
1"202Accepted"ResponseCodeThe202responseisaddedtotheSuccessheaderelddenition.
"202Accepted"hasthesamemeaningasthatdenedinHTTP/1.
1[6].
8.
3.
2"489BadEvent"ResponseCodeThe489eventresponseisaddedtotheClient-Errorheaderelddenition.
"489BadEvent"isusedtoindicatethattheserverdidnotunderstandtheeventpackagespeciedinaEventheadereld.
8.
4AugmentedBNFDenitionsTheAugmentedBNFdenitionsforthevariousnewandmodiedsyntaxelementsfollows.
ThenotationisasusedinSIP[2],andanyelementsnotdenedinthissectionareasdenedinSIPandthedocumentstowhichitrefers.
SUBSCRIBEm=%x53.
55.
42.
53.
43.
52.
49.
42.
45;{\SUBSCRIBE}incapsNOTIFYm=%x4E.
4F.
54.
49.
46.
59;{\NOTIFY}incapsextension-method=SUBSCRIBEm/NOTIFYm/tokenEvent=("Event"/"o")HCOLONevent-type*(SEMIevent-param)event-type=event-package*(".
"event-template)event-package=token-nodotevent-template=token-nodottoken-nodot=1*(alphanumevent-param=generic-param/("id"EQUALtoken)Allow-Events=("Allow-Events"/"u")HCOLONevent-type*(COMMAevent-type)Subscription-State="Subscription-State"HCOLONsubstate-value*(SEMIsubexp-params)substate-value="active"/"pending"/"terminated"/extension-substateextension-substate=tokensubexp-params=("reason"EQUALevent-reason-value)/("expires"EQUALdelta-seconds)/("retry-after"EQUALdelta-seconds)/generic-paramevent-reason-value="deactivated"/"probation"RoachStandardsTrack[Page28]RFC3265SIP-SpecicEventNoticationJune2002/"rejected"/"timeout"/"giveup"/"noresource"/event-reason-extensionevent-reason-extension=tokenNormativeReferences[1]S.
PetrackandL.
Conroy,"ThePINTserviceprotocol:ExtensionstoSIPandSDPforIPaccesstotelephonecallservices,"RFC2848,InternetEngineeringTaskForce,June2000.
[2]J.
Rosenberg,H.
Schulzrinne,G.
Camarillo,A.
Johnston,J.
Peterson,R.
Sparks,M.
Handley,andE.
Schooler,"SIP:sessioninitiationprotocol,"RFC3261,InternetEngineeringTaskForce,June2002.
[3]S.
Bradner,"KeywordsforuseinRFCstoindicaterequirementlevels,"RFC2119,InternetEngineeringTaskForce,Mar.
1997.
[4]M.
Day,S.
Aggarwal,G.
Mohr,andJ.
Vincent,"Instantmessaging/presenceprotocolrequirements,"RFC2779,InternetEngineeringTaskForce,Feb.
2000.
[5]T.
NartenandH.
Alvestrand,"GuidelinesforwritinganIANAconsiderationssectioninRFCs,"RFC2434,InternetEngineeringTaskForce,Oct.
1998.
[6]R.
Fielding,J.
Gettys,J.
Mogul,H.
Frystyk,L.
Masinter,P.
Leach,andT.
Berners-Lee,"Hypertexttransferprotocol–HTTP/1.
1,"RFC2616,InternetEngineeringTaskForce,June1999.
InformativeReferences[7]H.
SchulzrinneandJ.
Rosenberg,"Sessioninitiationprotocol(SIP)callerpreferencesandcalleecapa-bilities,"InternetDraft,InternetEngineeringTaskForce,July2002.
Workinprogress.
[8]J.
RosenbergandH.
Schulzrinne,"Guidelinesforauthorsofextensionstothesessioninitiationprotocol(SIP),"InternetDraft,InternetEngineeringTaskForce,June2002.
Workinprogress.
9AcknowledgementsThankstotheparticipantsintheEventsBOFatthe48thIETFmeetinginPittsburgh,aswellasthosewhogaveideasandsuggestionsontheSIPEventsmailinglist.
Inparticular,IwishtothankHenningSchulzrinneofColumbiaUniversityforcomingupwiththenalthree-tieredeventidenticationscheme,SeanOlsonformiscellaneousguidance,JonathanRosenbergforathoroughscrubbingofthe-00draft,andtheauthorsofthe"SIPExtensionsforPresence"documentfortheirinputtoSUBSCRIBEandNOTIFYrequestsemantics.
RoachStandardsTrack[Page29]RFC3265SIP-SpecicEventNoticationJune200210NoticeRegardingIntellectualPropertyRightsTheIETFhasbeennotiedofintellectualpropertyrightsclaimedinregardtosomeorallofthespec-icationcontainedinthisdocument.
Formoreinformation,consulttheonlinelistofclaimedrightsathttp://www.
ietf.
org/ipr.
html11Author'sAddressAdamRoachdynamicsoft5100TennysonParkwaySuite1200Plano,TX75024USAEMail:adam@dynamicsoft.
comVoice:sip:adam@dynamicsoft.
comFullCopyrightStatementCopyright(c)TheInternetSociety(2002).
AllRightsReserved.
Thisdocumentandtranslationsofitmaybecopiedandfurnishedtoothers,andderivativeworksthatcommentonorotherwiseexplainitorassistinitsimplementationmaybeprepared,copied,publishedanddistributed,inwholeorinpart,withoutrestrictionofanykind,providedthattheabovecopyrightnoticeandthisparagraphareincludedonallsuchcopiesandderivativeworks.
However,thisdocumentitselfmaynotbemodiedinanyway,suchasbyremovingthecopyrightnoticeorreferencestotheInternetSocietyorotherInternetorganizations,exceptasneededforthepurposeofdevelopingInternetstandardsinwhichcasetheproceduresforcopyrightsdenedintheInternetStandardsprocessmustbefollowed,orasrequiredtotranslateitintolanguagesotherthanEnglish.
ThelimitedpermissionsgrantedaboveareperpetualandwillnotberevokedbytheInternetSocietyoritssuccessorsorassigns.
Thisdocumentandtheinformationcontainedhereinisprovidedonan"ASIS"basisandTHEINTERNETSOCIETYANDTHEINTERNETENGINEERINGTASKFORCEDISCLAIMSALLWARRANTIES,EXPRESSORIMPLIED,INCLUDINGBUTNOTLIMITEDTOANYWARRANTYTHATTHEUSEOFTHEINFORMATIONHEREINWILLNOTINFRINGEANYRIGHTSORANYIMPLIEDWAR-RANTIESOFMERCHANTABILITYORFITNESSFORAPARTICULARPURPOSE.
AcknowledgementFundingfortheRFCEditorfunctioniscurrentlyprovidedbytheInternetSociety.
RoachStandardsTrack[Page30]
B.
RoachRequestforComments:3265dynamicsoftCategory:StandardsTrackJune2002Updates:2543SessionInitiationProtocol(SIP)-SpecicEventNoticationStatusofthisMemoThisdocumentspeciesanInternetstandardstrackprotocolfortheInternetcommunity,andrequestsdiscus-sionandsuggestionsforimprovements.
Pleaserefertothecurrenteditionofthe"InternetOfcialProtocolStandards"(STD1)forthestandardizationstateandstatusofthisprotocol.
Distributionofthismemoisunlimited.
CopyrightNoticeCopyright(c)TheInternetSociety(2002).
AllRightsReserved.
AbstractThisdocumentdescribesanextensiontotheSessionInitiationProtocol(SIP).
ThepurposeofthisextensionistoprovideanextensibleframeworkbywhichSIPnodescanrequestnoticationfromremotenodesindicatingthatcertaineventshaveoccurred.
Concreteusesofthemechanismdescribedinthisdocumentmaybestandardizedinthefuture.
NotethattheeventnoticationmechanismsdenedhereinareNOTintendedtobeageneral-purposeinfrastructureforallclassesofeventsubscriptionandnotication.
Contents1Introduction31.
1OverviewofOperation41.
2DocumentationConventions42Denitions53NodeBehavior53.
1DescriptionofSUBSCRIBEBehavior53.
1.
1SubscriptionDuration63.
1.
2IdenticationofSubscribedEventsandEventClasses63.
1.
3AdditionalSUBSCRIBEHeaderValues73.
1.
4SubscriberSUBSCRIBEBehavior73.
1.
5ProxySUBSCRIBEBehavior8RFC3265SIP-SpecicEventNoticationJune20023.
1.
6NotierSUBSCRIBEBehavior83.
2DescriptionofNOTIFYBehavior103.
2.
1IdenticationofReportedEvents,EventClasses,andCurrentState113.
2.
2NotierNOTIFYBehavior113.
2.
3ProxyNOTIFYBehavior123.
2.
4SubscriberNOTIFYBehavior123.
3General143.
3.
1DetectingsupportforSUBSCRIBEandNOTIFY143.
3.
2CANCELrequests143.
3.
3Forking143.
3.
4Dialogcreationandtermination143.
3.
5StateAgentsandNotierMigration153.
3.
6PollingResourceState153.
3.
7Allow-Eventsheaderusage163.
3.
8PINTCompatibility164EventPackages164.
1AppropriatenessofUsage164.
2EventTemplate-packages174.
3AmountofStatetobeConveyed174.
3.
1CompleteStateInformation174.
3.
2StateDeltas184.
4EventPackageResponsibilities184.
4.
1EventPackageName184.
4.
2EventPackageParameters184.
4.
3SUBSCRIBEBodies184.
4.
4SubscriptionDuration194.
4.
5NOTIFYBodies194.
4.
6NotierprocessingofSUBSCRIBErequests194.
4.
7NotiergenerationofNOTIFYrequests194.
4.
8SubscriberprocessingofNOTIFYrequests194.
4.
9Handlingofforkedrequests204.
4.
10Rateofnotications204.
4.
11StateAgents204.
4.
12Examples204.
4.
13UseofURIstoRetrieveState21RoachStandardsTrack[Page2]RFC3265SIP-SpecicEventNoticationJune20025SecurityConsiderations215.
1AccessControl215.
2NotierPrivacyMechanism215.
3Denial-of-Serviceattacks215.
4ReplayAttacks225.
5Man-in-themiddleattacks225.
6Condentiality226IANAConsiderations226.
1RegistrationInformation237RegistrationTemplate237.
1HeaderFieldNames247.
2ResponseCodes248Syntax258.
1NewMethods258.
1.
1SUBSCRIBEmethod268.
1.
2NOTIFYmethod268.
2NewHeaders278.
2.
1Eventheader278.
2.
2Allow-EventsHeader278.
2.
3Subscription-StateHeader278.
3NewResponseCodes288.
3.
1"202Accepted"ResponseCode288.
3.
2"489BadEvent"ResponseCode288.
4AugmentedBNFDenitions289Acknowledgements2910NoticeRegardingIntellectualPropertyRights3011Author'sAddress301IntroductionTheabilitytorequestasynchronousnoticationofeventsprovesusefulinmanytypesofSIPservicesforwhichcooperationbetweenend-nodesisrequired.
ExamplesofsuchservicesincludeautomaticcallbackRoachStandardsTrack[Page3]RFC3265SIP-SpecicEventNoticationJune2002services(basedonterminalstateevents),buddylists(basedonuserpresenceevents),messagewaitingindications(basedonmailboxstatechangeevents),andPSTNandInternetInternetworking(PINT)[1]status(basedoncallstateevents).
Themethodsdescribedinthisdocumentprovideaframeworkbywhichnoticationoftheseeventscanbeordered.
TheeventnoticationmechanismsdenedhereinareNOTintendedtobeageneral-purposeinfrastructureforallclassesofeventsubscriptionandnotication.
Meetingrequirementsforthegeneralproblemsetofsubscriptionandnoticationisfartoocomplexforasingleprotocol.
OurgoalistoprovideaSIP-specicframeworkforeventnoticationwhichisnotsocomplexastobeunusableforsimplefeatures,butwhichisstillexibleenoughtoprovidepowerfulservices.
Note,however,thateventpackagesbasedonthisframeworkmaydenearbitrarilyelaborateruleswhichgovernthesubscriptionandnoticationfortheeventsorclassesofeventstheydescribe.
Thisdocumentdoesnotdescribeanextensionwhichmaybeuseddirectly;itmustbeextendedbyotherdoc-uments(hereinreferredtoas"eventpackages").
Inobject-orienteddesignterminology,itmaybethoughtofasanabstractbaseclasswhichmustbederivedintoaninstantiatableclassbyfurtherextensions.
Guidelinesforcreatingtheseextensionsaredescribedinsection4.
1.
1OverviewofOperationThegeneralconceptisthatentitiesinthenetworkcansubscribetoresourceorcallstateforvariousresourcesorcallsinthenetwork,andthoseentities(orentitiesactingontheirbehalf)cansendnoticationswhenthosestateschange.
Atypicalowofmessageswouldbe:SubscriberNotifier|-----SUBSCRIBE---->|Requeststatesubscription200-Acknowledgesubscription|REFERENCES[RFC3265]Roach,A.
,"SIP-SpecificEventNotification",RFC3265,June2002.
7RegistrationTemplateTo:ietf-sip-events@iana.
orgSubject:RegistrationofnewSIPeventpackageRoachStandardsTrack[Page23]RFC3265SIP-SpecicEventNoticationJune2002PackageName:(Packagenamesmustconformtothesyntaxdescribedinsection\ref{sec:Event}.
)IsthisregistrationforaTemplatePackage:(indicateyesorno)PublishedSpecification(s):(TemplatepackagesrequireapublishedRFC.
Otherpackagesmayreferenceaspecificationwhenappropriate).
Person&emailaddresstocontactforfurtherinformation:7.
1HeaderFieldNamesThisdocumentregistersthreenewheadereldnames,describedelsewhereinthisdocument.
Theseheadersaredenedbythefollowinginformation,whichistobeaddedtotheheadersub-registryunderhttp://www.
iana.
org/aHeaderName:Allow-EventsCompactForm:uHeaderName:Subscription-StateCompactForm:(none)HeaderName:EventCompactForm:o7.
2ResponseCodesThisdocumentregisterstwonewresponsecodes.
Theseresponsecodesaredenedbythefollowinginfor-mation,whichistobeaddedtothemethodandresponse-codesub-registryunderhttp://www.
iana.
org/assignmentResponseCodeNumber:202DefaultReasonPhrase:AcceptedResponseCodeNumber:489DefaultReasonPhrase:BadEventRoachStandardsTrack[Page24]RFC3265SIP-SpecicEventNoticationJune20028SyntaxThissectiondescribesthesyntaxextensionsrequiredforeventnoticationinSIP.
Semanticsaredescribedinsection3.
NotethattheformalsyntaxdenitionsdescribedinthisdocumentareexpressedintheABNFformatusedinSIP[2],andcontainreferencestoelementsdenedtherein.
8.
1NewMethodsThisdocumentdescribestwonewSIPmethods:SUBSCRIBEandNOTIFY.
Thistableexpandsontables2and3inSIP[2].
HeaderWhereSUBNOTAcceptRooAccept2xx--Accept415ooAccept-EncodingRooAccept-Encoding2xx--Accept-Encoding415ooAccept-LanguageRooAccept-Language2xx--Accept-Language415ooAlert-InfoR--Alert-Info180--AllowRooAllow2xxooAllowrooAllow405mmAuthentication-Info2xxooAuthorizationRooCall-IDcmmContactRmmContact1xxooContact2xxmoContact3xxmmContact485ooContent-DispositionooContent-EncodingooContent-LanguageooContent-LengthttContent-Type**CSeqcmmDateooError-Info300-699ooRoachStandardsTrack[Page25]RFC3265SIP-SpecicEventNoticationJune2002Expireso-Expires2xxm-FromcmmIn-Reply-ToR--Max-ForwardsRmmMin-Expires423m-MIME-VersionooOrganizationo-PriorityRo-Proxy-Authenticate407mmProxy-AuthorizationRooProxy-RequireRooRAckR--Record-RouteRooRecord-Route2xx,401,484ooReply-To--RequireooRetry-After404,413,480,486ooRetry-After500,503ooRetry-After600,603ooRouteRccRSeq1xxooServerrooSubjectR--SupportedRooSupported2xxooTimestampooToc(1)mmUnsupported420ooUser-AgentooViacmmWarningR-oWarningrooWWW-Authenticate401mm8.
1.
1SUBSCRIBEmethodSUBSCRIBEisaddedtothedenitionoftheelementMethodintheSIPmessagegrammar.
LikeallSIPmethodnames,theSUBSCRIBEmethodnameiscasesensitive.
TheSUBSCRIBEmethodisusedtorequestasynchronousnoticationofaneventorsetofeventsatalatertime.
8.
1.
2NOTIFYmethodNOTIFYisaddedtothedenitionoftheelementMethodintheSIPmessagegrammar.
RoachStandardsTrack[Page26]RFC3265SIP-SpecicEventNoticationJune2002TheNOTIFYmethodisusedtonotifyaSIPnodethataneventwhichhasbeenrequestedbyanearlierSUBSCRIBEmethodhasoccurred.
Itmayalsoprovidefurtherdetailsabouttheevent.
8.
2NewHeadersThistableexpandsontables2and3inSIP[2],asamendedbythechangesdescribedinsection8.
1.
HeaderfieldwhereproxyACKBYECANINVOPTREGPRASUBNOTAllow-EventsRoo-ooooooAllow-Events2xx-o-ooooooAllow-Events489mmEventRmmSubscription-StateRm8.
2.
1EventheaderEventisaddedtothedenitionoftheelementmessage-headerintheSIPmessagegrammar.
ForthepurposesofmatchingresponsesandNOTIFYmessageswithSUBSCRIBEmessages,theevent-typeportionoftheEventheaderiscomparedbyte-by-byte,andtheidparametertoken(ifpresent)iscom-paredbyte-by-byte.
AnEventheadercontaininganidparameternevermatchesanEventheaderwithoutanidparameter.
Nootherparametersareconsideredwhenperformingacomparison.
Notethattheforgoingtextmeansthat"Event:foo;id=1234"wouldmatch"Event:foo;param=abcd;id=1234",butnot"Event:foo"(iddoesnotmatch)or"Event:Foo;id=1234"(eventportiondoesnotmatch).
Thisdocumentdoesnotdenevaluesforevent-types.
Thesevalueswillbedenedbyindividualeventpackages,andMUSTberegisteredwiththeIANA.
ThereMUSTbeexactlyoneeventtypelistedpereventheader.
Multipleeventspermessagearedisallowed.
8.
2.
2Allow-EventsHeaderAllow-Eventsisaddedtothedenitionoftheelementgeneral-headerintheSIPmessagegrammar.
Itsusageisdescribedinsection3.
3.
7.
8.
2.
3Subscription-StateHeaderSubscription-Stateisaddedtothedenitionoftheelementrequest-headerintheSIPmessagegrammar.
Itsusageisdescribedinsection3.
2.
4.
RoachStandardsTrack[Page27]RFC3265SIP-SpecicEventNoticationJune20028.
3NewResponseCodes8.
3.
1"202Accepted"ResponseCodeThe202responseisaddedtotheSuccessheaderelddenition.
"202Accepted"hasthesamemeaningasthatdenedinHTTP/1.
1[6].
8.
3.
2"489BadEvent"ResponseCodeThe489eventresponseisaddedtotheClient-Errorheaderelddenition.
"489BadEvent"isusedtoindicatethattheserverdidnotunderstandtheeventpackagespeciedinaEventheadereld.
8.
4AugmentedBNFDenitionsTheAugmentedBNFdenitionsforthevariousnewandmodiedsyntaxelementsfollows.
ThenotationisasusedinSIP[2],andanyelementsnotdenedinthissectionareasdenedinSIPandthedocumentstowhichitrefers.
SUBSCRIBEm=%x53.
55.
42.
53.
43.
52.
49.
42.
45;{\SUBSCRIBE}incapsNOTIFYm=%x4E.
4F.
54.
49.
46.
59;{\NOTIFY}incapsextension-method=SUBSCRIBEm/NOTIFYm/tokenEvent=("Event"/"o")HCOLONevent-type*(SEMIevent-param)event-type=event-package*(".
"event-template)event-package=token-nodotevent-template=token-nodottoken-nodot=1*(alphanumevent-param=generic-param/("id"EQUALtoken)Allow-Events=("Allow-Events"/"u")HCOLONevent-type*(COMMAevent-type)Subscription-State="Subscription-State"HCOLONsubstate-value*(SEMIsubexp-params)substate-value="active"/"pending"/"terminated"/extension-substateextension-substate=tokensubexp-params=("reason"EQUALevent-reason-value)/("expires"EQUALdelta-seconds)/("retry-after"EQUALdelta-seconds)/generic-paramevent-reason-value="deactivated"/"probation"RoachStandardsTrack[Page28]RFC3265SIP-SpecicEventNoticationJune2002/"rejected"/"timeout"/"giveup"/"noresource"/event-reason-extensionevent-reason-extension=tokenNormativeReferences[1]S.
PetrackandL.
Conroy,"ThePINTserviceprotocol:ExtensionstoSIPandSDPforIPaccesstotelephonecallservices,"RFC2848,InternetEngineeringTaskForce,June2000.
[2]J.
Rosenberg,H.
Schulzrinne,G.
Camarillo,A.
Johnston,J.
Peterson,R.
Sparks,M.
Handley,andE.
Schooler,"SIP:sessioninitiationprotocol,"RFC3261,InternetEngineeringTaskForce,June2002.
[3]S.
Bradner,"KeywordsforuseinRFCstoindicaterequirementlevels,"RFC2119,InternetEngineeringTaskForce,Mar.
1997.
[4]M.
Day,S.
Aggarwal,G.
Mohr,andJ.
Vincent,"Instantmessaging/presenceprotocolrequirements,"RFC2779,InternetEngineeringTaskForce,Feb.
2000.
[5]T.
NartenandH.
Alvestrand,"GuidelinesforwritinganIANAconsiderationssectioninRFCs,"RFC2434,InternetEngineeringTaskForce,Oct.
1998.
[6]R.
Fielding,J.
Gettys,J.
Mogul,H.
Frystyk,L.
Masinter,P.
Leach,andT.
Berners-Lee,"Hypertexttransferprotocol–HTTP/1.
1,"RFC2616,InternetEngineeringTaskForce,June1999.
InformativeReferences[7]H.
SchulzrinneandJ.
Rosenberg,"Sessioninitiationprotocol(SIP)callerpreferencesandcalleecapa-bilities,"InternetDraft,InternetEngineeringTaskForce,July2002.
Workinprogress.
[8]J.
RosenbergandH.
Schulzrinne,"Guidelinesforauthorsofextensionstothesessioninitiationprotocol(SIP),"InternetDraft,InternetEngineeringTaskForce,June2002.
Workinprogress.
9AcknowledgementsThankstotheparticipantsintheEventsBOFatthe48thIETFmeetinginPittsburgh,aswellasthosewhogaveideasandsuggestionsontheSIPEventsmailinglist.
Inparticular,IwishtothankHenningSchulzrinneofColumbiaUniversityforcomingupwiththenalthree-tieredeventidenticationscheme,SeanOlsonformiscellaneousguidance,JonathanRosenbergforathoroughscrubbingofthe-00draft,andtheauthorsofthe"SIPExtensionsforPresence"documentfortheirinputtoSUBSCRIBEandNOTIFYrequestsemantics.
RoachStandardsTrack[Page29]RFC3265SIP-SpecicEventNoticationJune200210NoticeRegardingIntellectualPropertyRightsTheIETFhasbeennotiedofintellectualpropertyrightsclaimedinregardtosomeorallofthespec-icationcontainedinthisdocument.
Formoreinformation,consulttheonlinelistofclaimedrightsathttp://www.
ietf.
org/ipr.
html11Author'sAddressAdamRoachdynamicsoft5100TennysonParkwaySuite1200Plano,TX75024USAEMail:adam@dynamicsoft.
comVoice:sip:adam@dynamicsoft.
comFullCopyrightStatementCopyright(c)TheInternetSociety(2002).
AllRightsReserved.
Thisdocumentandtranslationsofitmaybecopiedandfurnishedtoothers,andderivativeworksthatcommentonorotherwiseexplainitorassistinitsimplementationmaybeprepared,copied,publishedanddistributed,inwholeorinpart,withoutrestrictionofanykind,providedthattheabovecopyrightnoticeandthisparagraphareincludedonallsuchcopiesandderivativeworks.
However,thisdocumentitselfmaynotbemodiedinanyway,suchasbyremovingthecopyrightnoticeorreferencestotheInternetSocietyorotherInternetorganizations,exceptasneededforthepurposeofdevelopingInternetstandardsinwhichcasetheproceduresforcopyrightsdenedintheInternetStandardsprocessmustbefollowed,orasrequiredtotranslateitintolanguagesotherthanEnglish.
ThelimitedpermissionsgrantedaboveareperpetualandwillnotberevokedbytheInternetSocietyoritssuccessorsorassigns.
Thisdocumentandtheinformationcontainedhereinisprovidedonan"ASIS"basisandTHEINTERNETSOCIETYANDTHEINTERNETENGINEERINGTASKFORCEDISCLAIMSALLWARRANTIES,EXPRESSORIMPLIED,INCLUDINGBUTNOTLIMITEDTOANYWARRANTYTHATTHEUSEOFTHEINFORMATIONHEREINWILLNOTINFRINGEANYRIGHTSORANYIMPLIEDWAR-RANTIESOFMERCHANTABILITYORFITNESSFORAPARTICULARPURPOSE.
AcknowledgementFundingfortheRFCEditorfunctioniscurrentlyprovidedbytheInternetSociety.
RoachStandardsTrack[Page30]
- mailbox403forbidden相关文档
- propertyMapFromFile403forbidden
- times403forbidden
- signicant403forbidden
- AccuRevGitCentric403forbidden
- pandemic403forbidden
- 请求403forbidden
瓜云互联：全场9折优惠,香港CN2、洛杉矶GIA高防vps套餐,充值最高返300元
瓜云互联怎么样?瓜云互联之前商家使用的面板为WHMCS，目前商家已经正式更换到了魔方云的面板，瓜云互联商家主要提供中国香港和美国洛杉矶机房的套餐，香港采用CN2线路直连大陆，洛杉矶为高防vps套餐，三网回程CN2 GIA，提供超高的DDOS防御，瓜云互联商家承诺打死退款，目前商家提供了一个全场9折和充值的促销，有需要的朋友可以看看。点击进入：瓜云互联官方网站瓜云互联促销优惠：9折优惠码：联系在线客...
标准互联（450元）襄阳电信100G防御服务器 10M独立带宽
目前在标准互联这边有两台香港云服务器产品，这不看到有通知到期提醒才关注到。平时我还是很少去登录这个服务商的，这个服务商最近一年的促销信息比较少，这个和他们的运营策略有关系。已经从开始的倾向低价和个人用户云服务器市场，开始转型到中高端个人和企业用户的独立服务器。在这篇文章中，有看到标准互联有推出襄阳电信高防服务器100GB防御。有三款促销方案我们有需要可以看看。我们看看几款方案配置。型号内存硬盘IP...
gcorelabs：CDN业务节点分布100多个国家地区，免费版提供1T/月流量
卢森堡商家gcorelabs是个全球数据中心集大成的运营者，不但提供超过32个数据中心的VPS、13个数据中心的cloud（云服务器）、超过44个数据中心的独立服务器，还提供超过100个数据中心节点的CDN业务。CDN的总带宽容量超过50Tbps，支持免费测试！ Gcorelabs根据业务分，有2套后台，分别是： CDN、流媒体平台、DDoS高防业务、块存储、cloud云服务器、裸金属服务器...
403forbidden为你推荐
-
involving网易yeah现有新的ios更新可用请从ios14be苹果手机怎么更新到14access数据库修复Access数据库恢复，有些表被损坏或有些表的部分记录被损坏，求解啊企业ssl证书国内哪些公司是专门做ssl证书的呢?中国企业信息网哪个查询企业信息的网站收录的企业信息最多传奇域名谁能帮忙查查传奇的IP和域名泉州商标注册泉州本地商标注册要怎么注册？具体流程是什么？中国保健养猪网135保健养猪，135天可以出栏吗？店铺统计怎样查淘宝店铺的销售总额网上支付功能网银有什么功能？