TITLE

Why can't we all get along?

AUTHOR(S)
Bradner, Scott
PUB. DATE
December 1998
SOURCE
Network World;12/21/98, Vol. 15 Issue 51, p36
SOURCE TYPE
Trade Publication
DOC. TYPE
Article
ABSTRACT
Focuses on the cooperation among Internet standards organizations as of December 21, 1998. Partnership between the Internet Engineering Task Force and the International Telecommunication Union; Other groups' efforts to promote cooperation.
ACCESSION #
2542262

 

Related Articles

  • A CLOSER LOOK AT THE INTERNET'S STANDARDS SETTING PROCESS. Jakobs, Kai // Proceedings of the IADIS International Conference on WWW/Interne;Jan2003, p557 

    The Internet has emerged as a crucial part of the Global Information Infrastructure. This is not least due to the remarkable longevity and versatility of some of its protocols. Accordingly, there have been many claims that the standards setting process adopted by the Internet community is vastly...

  • Standards evolve for IP telephony. Hui-Lan Lu // Lightwave;Dec99, Vol. 16 Issue 13, p22 

    Focuses on the evolution of standards for Internet protocol (IP) telephony. Suite of standards from the International Telecommunication Union-Telecommunication; Session initiation protocol from the Internet Engineering Task Force; Differences of the public-switched telephone network from IP...

  • 3GPP forges relationships with ITU, IETF.  // RCR Wireless News;12/4/2000, Vol. 19 Issue 49, p22 

    Reports on the Third Generation Project Partnership's entry into working relationships with the International Telecommunication Union and the Internet Engineering Task Force.

  • RMon to the rescue. Carr, Jim // InfoWorld;12/12/94, Vol. 16 Issue 50, p1 

    Presents information on the Internet Engineering Task Force's remote monitoring (RMon) standard. Features; Hardware requirements; Product support; Performance. INSET: Can't afford constant monitoring?..

  • Light at end of IPv6 tunnel. Surkan, Michael // PC Week;01/26/98, Vol. 15 Issue 4, p85 

    States that the Internet Engineering Task Force appears ready to move the core IP Version 6 specification to a draft standard. Decision to come by the end of 1998; The difference between IP Version 6 specification and any other IETF proposal; What Version 6 modifications provide for.

  • IETF agrees on 16-byte addressing. Musich, Paula // PC Week;8/8/94, Vol. 11 Issue 31, p13 

    Reports that the Internet Engineering Task Force (IETF) has laid a groundwork for the next version of the Internet Protocol (IP) to avert a protocol address shortage. Address expansion from four to 16 bytes; Benefits of address expansion; Allocation architecture for the 16-byte addressing...

  • Briefly noted.  // InfoWorld;11/21/94, Vol. 16 Issue 47, p3 

    Reports on the Internet Engineering Task Force's approval of the IP next generation protocol.

  • IETF Clears Roadblock To Routing Standard. McGarvey, Joe // Inter@ctive Week;03/01/99, Vol. 6 Issue 9, p17 

    Focuses on the compromise reached by members of the Multiprotocol Label Switching (MPLS) working group within the Internet Engineering Task Force (IETF) for router-to-router communication. Design of the MPLS; Major value of the MPLS to service providers; Expected finalization of the standard.

  • Standard Policy Management Proposed. McGarvey, Joe // Inter@ctive Week;02/07/2000, Vol. 7 Issue 5, p50 

    Reports on the proposal of the Internet Engineering Task Force (IETF) to adopt a portion of the Common Open Policy Server (COPS) protocol as industry standard. Function of the COPS protocol; Emergence of policy-based management as a vital tool for service providers; Benefits of the protocol.

Share

Read the Article

Courtesy of VIRGINIA BEACH PUBLIC LIBRARY AND SYSTEM

Sorry, but this item is not currently available from your library.

Try another library?
Sign out of this library

Other Topics