S. Floyd and L. Diagle. IAB Architectural and Policy Considerations for Open Pluggable Edge Services. In IETF Request for Comments -- RFC 3238, January 2002. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Network Working Group S. Floyd, Editor Request for Comments.. - Status Of This Self-citation (Floyd) (Correct)
.... as it moved through the network , and that therefore the risks of OPES outweighed the benefits [CDT01] As one consequence of this debate, the IAB wrote a document on IAB Architectural and Policy Considerations for OPES , considering both the potential architectural benefits and costs of OPES [RFC3238]. This document did not recommend specific solutions or mandate specific functional requirements, but instead included recommendations of issues such as concerns about data integrity that OPES solutions standardized in the IETF should be required to address. 9. General Robustness Questions ....
Floyd, S. and L. Daigle, "IAB Architectural and Policy Considerations for Open Pluggable Edge Services", RFC 3238, January 2002.
Internet Engineering Task Force S. Floyd, Editor INTERNET.. - Status Of This Self-citation (Floyd) (Correct)
.... as it moved through the network , and that therefore the risks of OPES outweighed the benefits [CDT01] As one consequence of this debate, the IAB wrote a document on IAB Architectural and Policy Considerations for OPES , considering both the potential architectural benefits and costs of OPES [RFC3238]. This document did not recommend specific solutions or mandate specific functional requirements, but instead included recommendations of issues such as concerns about data integrity that OPES solutions standardized in the IETF should be required to address. 9. General Robustness Questions ....
S. Floyd and L. Daigle, "IAB Architectural and Policy Considerations for Open Pluggable Edge Services", RFC 3238, Informational, January 2002.
Internet Engineering Task Force S. Floyd, Editor.. -.. Self-citation (Floyd) (Correct)
.... as it moved through the network , and that therefore the risks of OPES outweighed the benefits [CDT01] As one consequence of this debate, the IAB wrote a document on IAB Architectural and Policy Considerations for OPES , considering both the potential architectural benefits and costs of OPES [RFC3238]. This document did not recommend specific solutions or mandate specific functional requirements, but instead included recommendations of issues such as concerns about data integrity that OPES solutions standardized in the IETF should be required to address. 11.3. Case Study: Stresses on DNS. ....
S. Floyd and L. Daigle, "IAB Architectural and Policy Considerations for Open Pluggable Edge Services", RFC 3238, Informational, January 2002.
General Architectural and Policy Considerations - Floyd (2002) Self-citation (Floyd) (Correct)
.... as it moved through the network , and that therefore the risks of OPES outweighed the benefits [CDT01] As one consequence of this debate, the IAB wrote a document on IAB Architectural and Policy Considerations for OPES , considering both the potential architectural benefits and costs of OPES [RFC3238]. This document did not recommend specific solutions or mandate specific functional requirements, but instead included recommendations of issues such as concerns about data integrity that OPES solutions standardized in the IETF should be required to address. 11.3. Case Study: Stresses on DNS. ....
S. Floyd and L. Daigle, "IAB Architectural and Policy Considerations for Open Pluggable Edge Services", RFC 3238, Informational, January 2002.
Optimizing Web Delivery over Wireless Links: Design.. - Chakravorty, Clark.. (2005) (Correct)
No context found.
S. Floyd and L. Diagle. IAB Architectural and Policy Considerations for Open Pluggable Edge Services. In IETF Request for Comments -- RFC 3238, January 2002.
Proxy-based Flow Aggregation for Enhanced TCP over GPRS - Chakravorty, Katti.. (2003) (Correct)
No context found.
S. Floyd and L. Diagle, "IAB Architectural and Policy Considerations for Open Pluggable Edge Services", Request for Comments, RFC 3238, January 2002.
Considerations from the Service Management Research Group.. - Eder, Chaskar, Nag (2002) (2 citations) (Correct)
No context found.
Floyd, S. and L. Daigle, "IAB Architectural and Policy Considerations for Open Pluggable Edge Services", RFC 3238, January 2002.
Unknown - Use Cases And (Correct)
No context found.
Floyd, S. and L. Daigle, "IAB Architectural and Policy Considerations for Open Pluggable Edge Services", RFC 3238, January 2002.
Network Working Group J. Klensin Request for Comments: 3467.. - Role Of The (Correct)
No context found.
Floyd, S. and L. Daigle, "IAB Architectural and Policy Considerations for Open Pluggable Edge Services", RFC 3238, January 2002.
Network Working Group J. Kempf, Ed. Request for Comments.. - Reflections On The (Correct)
No context found.
Floyd, S. and L. Daigle, "IAB Architectural and Policy Considerations for Open Pluggable Edge Services", RFC 3238, January 2002.
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