[Sysops-list] [Fwd: [rfc-dist] RFC 5136 on Defining Network Capacity]

[Gaurab Raj Upadhaya]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

good new document.

thanks
~ -gaurab


- -------- Original Message --------
Subject: [rfc-dist] RFC 5136 on Defining Network Capacity
Date: Tue, 12 Feb 2008 11:59:33 -0800 (PST)
From: rfc-editor at rfc-editor.org
To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org
CC: ippm at ietf.org, rfc-editor at rfc-editor.org


A new Request for Comments is now available in online RFC libraries.


~        RFC 5136

~        Title:      Defining Network Capacity
~        Author:     P. Chimento, J. Ishac
~        Status:     Informational
~        Date:       February 2008
~        Mailbox:    Philip.Chimento at jhuapl.edu,
~                    jishac at nasa.gov
~        Pages:      14
~        Characters: 30682
~        Updates/Obsoletes/SeeAlso:   None

~        I-D Tag:    draft-ietf-ippm-bw-capacity-05.txt

~        URL:        http://www.rfc-editor.org/rfc/rfc5136.txt

Measuring capacity is a task that sounds simple, but in reality can
be quite complex.  In addition, the lack of a unified nomenclature on
this subject makes it increasingly difficult to properly build, test,
and use techniques and tools built around these constructs.  This
document provides definitions for the terms 'Capacity' and 'Available
Capacity' related to IP traffic traveling between a source and
destination in an IP network.  By doing so, we hope to provide a
common framework for the discussion and analysis of a diverse set of
current and future estimation techniques.  This memo provides information
for the Internet community.

This document is a product of the IP Performance Metrics
Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body

help: ways_to_get_rfcs. For example:

~        To: rfc-info at RFC-EDITOR.ORG
~        Subject: getting rfcs

~        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
rfc-dist mailing list
rfc-dist at rfc-editor.org
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHsmdqSo7fU26F3X0RAg+pAKDmY4Wp7ICaqBrZYlgbGBNsQUTjVQCfdojk
xdgS65vxq7vdhk2DcBS79TE=
=5yij
-----END PGP SIGNATURE-----