18 citations found. Retrieving documents...
Newman, C. and J. G. Myers, "ACAP -- Application Configuration Access Protocol", RFC 2244, November 1997.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Mobile networking in the Internet - Perkins (1998)   (8 citations)  (Correct)

....new point of at C.E. Perkins Mobile networking in the Internet 331 tachment to the Internet are probably so varied and difficult to classify that we cannot make a very good analysis of future developments in this area. Perhaps protocols such as ACAP (Application Configuration Access Protocol [36]) will help us organize our directions. On the other hand, other kinds of environmental interactions are less related to user application profiles, and more related to the user s constantly changing need for information. For instance, it doesn t make much sense to route the user s data to a local ....

C. Newman and J.G. Myers, ACAP -- application configuration access protocol, RFC 2244 (November 1997).


Service Templates and Service: Schemes - Guttman, Perkins, Kempf (1999)   (22 citations)  (Correct)

....The attr list field is composed of a list of semicolon ( separated attribute assignments of the form: attr id = attr value or for keyword attributes: attr id Attributes are part of service: URLs when the attributes are required to access a particular service. For instance, an ACAP [13] service might require that the client authenticate with it through Kerberos. Including an attribute in the service registration allows the ACAP client to make use of the correct SASL [11] authentication mechanism. The ACAP server s registration might look like: ....

Newman C. and J. Myers, "ACAP -- Application Configuration Access Protocol", RFC 2244, November 1997.


Transporting User Control Information in SIP REGISTER Payloads - Lennox, Schulzrinne (2000)   (Correct)

....clients. This technique is not appropriate for all environments most obviously, it is not useful for H.323 [4] servers and we do not anticipate that it will be the only such transport mechanism developed. Other protocols considered have included transporting scripts over LDAP [5] ACAP [6], or HTTP file upload [7] or transport mechanisms developed from scratch. The advantages of this technique, over these other possible methods for transfering scripts to a registration server, are twofold. First of all, a SIP client already needs to know the registrar and addresses to use in ....

C. Newman and J. G. Myers, "ACAP -- application configuration access protocol," Request for Comments 2244, Internet Engineering Task Force, Nov. 1997.


Transporting User Control Information in SIP REGISTER Payloads - Lennox, Schulzrinne (2000)   (Correct)

....clients. This technique is not appropriate for all environments most obviously, it is not useful for H.323 [4] servers and we do not anticipate that it will be the only such transport mechanism developed. Other protocols considered have included transporting scripts over LDAP [5] ACAP [6], or HTTP file upload [7] or transport mechanisms developed from scratch. 2 Conventions Of This Document In this document, the key words MUST , MUST NOT , REQUIRED , SHALL , SHALL NOT , SHOULD , SHOULD NOT , RECOMMENDED , MAY , and OPTIONAL are to be interpreted as described in RFC ....

C. Newman and J. G. Myers, "ACAP -- application configuration access protocol," Request for Comments (Proposed Standard) 2244, Internet Engineering Task Force, Nov. 1997.


CPL: A Language for User Control of Internet Telephony Services - Lennox, Schulzrinne (1999)   (13 citations)  (Correct)

....i;octet, indicating literal comparison of UTF 8 octets, and i;asciicasemap, which indicates that alphabetic characters in the US ASCII range should have their upper and lower cases compared the same. If no comparitor is specified, i;ascii casemap is assumed. Comparators are defined by ACAP [7]; for more information, see that specification. CPL servers SHOULD verify at script submission time that all requested comparators are supported by the server. The naming scheme of comparators is as defined by ACAP; the motivation of the i; prefix of the comparators is unclear, but it seems to ....

J. Myers and C. Newman, "ACAP -- application configuration access protocol," Request for Comments (Proposed Standard) 2244, Internet Engineering Task Force, Dec. 1997.


CPL: A Language for User Control of Internet Telephony Services - Lennox, Schulzrinne (1999)   (13 citations)  (Correct)

....i;octet, indicating literal comparison of UTF 8 octets, and i;asciicasemap, which indicates that alphabetic characters in the US ASCII range should have their upper and lower cases compared the same. If no comparitor is specified, i;ascii casemap is assumed. Comparators are defined by ACAP [7]; for more information, see that specification. CPL servers SHOULD verify at script submission time that all requested comparators are supported by the server. The naming scheme of comparators is as defined by ACAP; the motivation of the i; prefix of the comparators is unclear, but it seems to ....

J. Myers and C. Newman, "ACAP -- application configuration access protocol," Request for Comments (Proposed Standard) 2244, Internet Engineering Task Force, Dec. 1997.


Status of this Memo - Me Mo   (Correct)

....Internet based open standard mechanisms can provide an extensible platform for further carrier service offerings, enhanced interoperability among back end services, and vendor independence. This paper describes a viable and attractive means to provide OTASP OTAPA via IS 707, using the ACAP [ACAP] protocol. RFC 2636 OTASP OTAPA via ACAP July 1999 Gellens Informational Page 2 Table of Contents 1. Terms . 4 2. Feature ....

....the mobile station has acquired CDMA service on the carrier s network and the notification has reached the mobile station. Alternatively, OTAPA can be handled by including a recheck interval in the set of data used to provision the mobile station. When using a low overhead protocol, such as ACAP [ACAP] , it is reasonable to have a mobile station check in periodically to see if anything has changed. The time of day and or day of week that such rechecks should occur could be included in the provisioning data. OTAPA activity can be terminated at any time due to user call activity. RFC 2636 ....

Newman, C., and J. Myers, "ACAP -- Application Configuration Access Protocol", RFC 2244, November 1997.


Transporting User Control Information in SIP REGISTER Payloads - Lennox, Schulzrinne (1999)   (Correct)

....and clients. This technique is not appropriate for all environments most obviously, it is not useful for H.323 [4] servers and we do not anticipate that it will be the only such transport mechanism developed. Other protocols considered have included transporting scripts over LDAP [5] ACAP [6], or HTTP file upload [7] or transport mechanisms developed from scratch. 2 Transport Details To upload a script, the registration client places the script in the body of the SIP REGISTER request. Bodies of SIP requests are described in [3] The Content Type header field is set to the media type ....

J. Myers and C. Newman, "ACAP -- application configuration access protocol," Request for Comments (Proposed Standard) 2244, Internet Engineering Task Force, Dec. 1997.


Unknown -   Self-citation (Newman)   (Correct)

No context found.

Newman, C. and J. Myers, "ACAP -- Application Configuration Access Protocol", RFC 2244, November 1997.


Network Working Group C. Newman Request for Comments.. - The One-Time-Password..   Self-citation (Newman)   (Correct)

No context found.

Newman, C. and J. Myers, "ACAP -- Application Configuration Access Protocol", RFC 2244, November 1997.


Network Working Group T. Showalter Request for Comments: 3028 .. - Status Of This   (Correct)

No context found.

Newman, C. and J. G. Myers, "ACAP -- Application Configuration Access Protocol", RFC 2244, November 1997.


Network Working Group C. Daboo Request for Comments: 3685.. - Status Of This   (Correct)

No context found.

Newman, C. and J. Myers, "ACAP -- Application Configuration Access Protocol", RFC 2244, November 1997.


Unknown -   (Correct)

No context found.

Newman, C., and J. Myers, "ACAP -- Application Configuration Access Protocol", RFC 2244, November 1997.


Unknown -   (Correct)

No context found.

Newman, C. and J. Myers, "ACAP -- Application Configuration Access Protocol", RFC 2244, November 1997.


Network Working Group M. Rose Request for Comments: 3117.. - Status Of This   (Correct)

No context found.

Newman, C. and J. Myers, "ACAP -- Application Configuration Access Protocol", RFC 2244, November 1997.


Unknown -   (Correct)

No context found.

Myers, J. "ACAP -- Application Configuration Access Protocol", Work in Progress.


Unknown -   (Correct)

No context found.

Newman, C. and J. Myers, "ACAP -- Application Configuration Access Protocol", RFC 2244, November 1997.


QoS and Delivery Context in Rule-Based Edge Services - Ng Chan Wah   (Correct)

No context found.

Newman, C., and Myers, J. G., "ACAP -- Application Configuration Access Protocol", IETF RFC 2244, http://www.ietf.org/rfc/rfc2244.txt, November 1997.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC