draft-ietf-diffserv-pdb-bh-01.txt   draft-ietf-diffserv-pdb-bh-02.txt 
Internet Engineering Task Force B. Carpenter Internet Engineering Task Force B. Carpenter
Differentiated Services Working Group IBM Differentiated Services Working Group IBM
Internet Draft K. Nichols Internet Draft K. Nichols
Expires in June, 2001 Packet Design Expires in July, 2001 Packet Design
A Bulk Handling Per-Domain Behavior for Differentiated Services A Bulk Handling Per-Domain Behavior for Differentiated Services
<draft-ietf-diffserv-pdb-bh-02>
<draft-ietf-diffserv-pdb-bh-01>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at and may be updated, replaced, or obsoleted by other documents at
any time. It is inappropriate to use Internet-Drafts as reference any time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This document is a product of the Diffserv working group. Comments This document is a product of the Diffserv working group. Comments
on this draft should be directed to the Diffserv mailing list on this draft should be directed to the Diffserv mailing list
<diffserv@ietf.org>. The list of current Internet-Drafts can be accessed <diffserv@ietf.org>. The list of current Internet-Drafts can be
at www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft accessed at www.ietf.org/ietf/1id-abstracts.txt.
Shadow Directories can be accessed at www.ietf.org/shadow.html. The list of Internet-Draft Shadow Directories can be accessed at
Distribution of this memo is unlimited. www.ietf.org/shadow.html. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2000). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract Abstract
This document proposes a differentiated services per-domain behavior This document proposes a differentiated services per-domain behavior
whose traffic may be "starved" (although starvation is not strictly whose traffic may be "starved" (although starvation is not strictly
required) in a properly functioning network. This is in contrast required) in a properly functioning network. This is in contrast
to the Internet's "best-effort" or "normal Internet traffic" model. to the Internet's "best-effort" or "normal Internet traffic" model.
The name, "bulk handling" is loosely based on the United States' The name, "bulk handling" is loosely based on the United States'
Postal Service term for very low priority mail, sent at a reduced Postal Service term for very low priority mail, sent at a reduced
rate. This document gives some example uses, but does not propose rate. This document gives some example uses, but does not propose
skipping to change at line 75 skipping to change at line 73
in a differentiated services domain. in a differentiated services domain.
The name, "bulk handling" is loosely based on the United States The name, "bulk handling" is loosely based on the United States
Postal Service's Bulk Handling deliver for mail: a lower-cost delivery Postal Service's Bulk Handling deliver for mail: a lower-cost delivery
where the items are not handled with the same care or delivered where the items are not handled with the same care or delivered
with the same timeliness as items with first-class postage. There with the same timeliness as items with first-class postage. There
is no intrinsic reason to limit the applicability of the BH PDB is no intrinsic reason to limit the applicability of the BH PDB
to any particular application or type of traffic. It is intended to any particular application or type of traffic. It is intended
as an additional tool for administrators in engineering networks. as an additional tool for administrators in engineering networks.
Note: where not otherwise defined, terminology used in this Note: where not otherwise defined, terminology used in this document
document is defined in [RFC2474]. is defined in [RFC2474].
2 Applicability 2 Applicability
A Bulk Handling (BH) PDB is for sending extremely non-critical traffic A Bulk Handling (BH) PDB is for sending extremely non-critical traffic
across a DS domain or DS region. There should be an expectation across a DS domain or DS region. There should be an expectation
that packets of the BH PDB may be delayed or dropped when any other that packets of the BH PDB may be delayed or dropped when any other
traffic is present. Its use might assist a network operator in traffic is present. Its use might assist a network operator in
moving certain kinds of traffic or users to off-peak times. moving certain kinds of traffic or users to off-peak times.
Alternatively, or in addition, packets can be designated for the BH PDB Alternatively, or in addition, packets can be designated for the BH PDB
where the goal is to protect all other packet traffic from competition where the goal is to protect all other packet traffic from competition
skipping to change at line 216 skipping to change at line 214
2. For Netnews and other "bulk mail" of the Internet. 2. For Netnews and other "bulk mail" of the Internet.
3. For "downgraded" traffic from some other PDB. 3. For "downgraded" traffic from some other PDB.
4. For content distribution, Napster traffic, and the like. 4. For content distribution, Napster traffic, and the like.
8 Experiences 8 Experiences
The authors solicit experiences for this section. The authors solicit experiences for this section.
9 Acknowledgments 9 Security Considerations for BH PDB
There are no specific security exposures for this PDB. See the general
security considerations in [RFC2474] and [RFC2475].
10 Acknowledgments
The notion of having something "lower than Best Effort" was raised The notion of having something "lower than Best Effort" was raised
in the Diffserv Working Group, most notably by Roland Bless and in the Diffserv Working Group, most notably by Roland Bless and
Klaus Wehrle in their Internet Draft [LBE] and by Yoram Bernet Klaus Wehrle in their Internet Draft [LBE] and by Yoram Bernet
for enterprise multimedia applications. Previous discussion centered for enterprise multimedia applications. Previous discussion centered
on the creation of a new PHB which the authors believe is not required. on the creation of a new PHB which the authors believe is not required.
This document was specifically written to explain how to get less This document was specifically written to explain how to get less
than Best Effort without a new PHB. than Best Effort without a new PHB.
Yoram Bernet contributed significant text for the "Applications" Yoram Bernet contributed significant text for the "Examples" section
section of this document and other useful comments that helped of this document and other useful comments that helped in editing.
in editing. Other Diffserv WG members suggested that the BH PDB Other Diffserv WG members suggested that the BH PDB is needed for
is needed for Napster traffic, particularly at universities. Napster traffic, particularly at universities.
References References
[PDBDEF] "Definition of Differentiated Services Per-Domain Behaviors [PDBDEF] "Definition of Differentiated Services Per-Domain Behaviors
and Rules for their Specification", K. Nichols, B. Carpenter, and Rules for their Specification", K. Nichols, B. Carpenter,
draft-ietf-diffserv-pdb-def-02.txt draft-ietf-diffserv-pdb-def-03.txt
[RFC2474] RFC 2474, "Definition of the Differentiated Services Field [RFC2474] RFC 2474, "Definition of the Differentiated Services Field
(DS Field) in the IPv4 and IPv6 Headers", K.Nichols, S. Blake, (DS Field) in the IPv4 and IPv6 Headers", K.Nichols, S. Blake,
F. Baker, D. Black, www.ietf.org/rfc/rfc2474.txt F. Baker, D. Black, www.ietf.org/rfc/rfc2474.txt
[RFC2475] RFC 2475, "An Architecture for Differentiated Services", [RFC2475] RFC 2475, "An Architecture for Differentiated Services",
S. Blake, D. Black, M.Carlson, E.Davies, Z.Wang,W.Weiss, S. Blake, D. Black, M.Carlson, E.Davies, Z.Wang,W.Weiss,
www.ietf.org/rfc/rfc2475.txt www.ietf.org/rfc/rfc2475.txt
[RFC2597] RFC 2597, "Assured Forwarding PHB Group", F. Baker, J. [RFC2597] RFC 2597, "Assured Forwarding PHB Group", F. Baker, J.
Heinanen, W. Weiss, J. Wroclawski, www.ietf.org/rfc/rfc2597.txt Heinanen, W. Weiss, J. Wroclawski, www.ietf.org/rfc/rfc2597.txt
[CBQ] S. Floyd and V. Jacobson, Link-sharing and Resource Management [CBQ] S. Floyd and V. Jacobson, Link-sharing and Resource Management
Models for Packet Networks, IEEE/ACM Transactions on Networking, Models for Packet Networks, IEEE/ACM Transactions on Networking,
Vol. 3 No. 4, pp. 365-386, August 1995 Vol. 3 No. 4, pp. 365-386, August 1995
[LBE] A Lower Than Best-Effort Per-Hop Behavior, [LBE] "A Lower Than Best-Effort Per-Hop Behavior",
draft-bless-diffserv-phb-lbe-00.txt, R. Bless and K. Wehrle, 1999,
(work in progress) (work in progress).
Authors' Addresses Authors' Addresses
Brian Carpenter Kathleen Nichols Brian Carpenter Kathleen Nichols
IBM Packet Design, Inc. IBM Packet Design
c/o ICAIR 66 Willow Place c/o iCAIR 66 Willow Place
Suite 150 Menlo Park, CA 94025 Suite 150 Menlo Park, CA 94025
1890 Maple Avenue USA 1890 Maple Avenue USA
Evanston, IL 60201 Evanston, IL 60201
USA USA
email: brian@icair.org email: nichols@packetdesign.com email: brian@icair.org email: nichols@packetdesign.com
 End of changes. 10 change blocks. 
22 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/