draft-ietf-msgtrk-mtqp-07.txt   draft-ietf-msgtrk-mtqp-08.txt 
Internet Draft T. Hansen Internet Draft T. Hansen
draft-ietf-msgtrk-mtqp-07.txt AT&T Laboratories draft-ietf-msgtrk-mtqp-08.txt AT&T Laboratories
Valid for six months April 9, 2002 Valid for six months May 19, 2002
Message Tracking Query Protocol Message Tracking Query Protocol
<draft-ietf-msgtrk-mtqp-07.txt> <draft-ietf-msgtrk-mtqp-08.txt>
Authors' version: 1.17 Authors' version: 1.18
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. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 15, line 51 skipping to change at page 15, line 51
option parameters option parameters
added commands added commands
standard commands affected standard commands affected
specification reference specification reference
discussion discussion
One MTQP option is defined in this document, with the following One MTQP option is defined in this document, with the following
registration definition: registration definition:
option identifier: STARTTLS option identifier: STARTTLS
option parameters: hostname option parameters: none
added commands: STARTTLS added commands: STARTTLS
standard commands affected: none standard commands affected: none
specification reference: RFC TBD specification reference: RFC TBD
discussion: see RFC TBD discussion: see RFC TBD
Additional vendor-specific options for this protocol have names Additional vendor-specific options for this protocol have names
that begin with "vnd.". After the "vnd." would appear the reversed that begin with "vnd.". After the "vnd." would appear the reversed
domain name of the vendor, another dot ".", and a name for the option domain name of the vendor, another dot ".", and a name for the option
itself. For example, "vnd.com.example.extinfo" might represent a itself. For example, "vnd.com.example.extinfo" might represent a
vendor-specific extension providing extended information by the owner of vendor-specific extension providing extended information by the owner of
skipping to change at page 20, line 15 skipping to change at page 20, line 15
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on This document and the information contained herein is provided on
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT
NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL
NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. FITNESS FOR A PARTICULAR PURPOSE.
This document expires October 9, 2002. This document expires November 19, 2002.
 End of changes. 5 change blocks. 
5 lines changed or deleted 5 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/