[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

I-D ACTION:draft-terrell-iptx-dhcp-req-iptx-ip-add-spec-00.txt,.pdf

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title		: The IPtX Dynamic Host Configuration Protocol (IPtX 
                          DHCP), and the Requirements for the 'IPtX' IP 
                          Addressing Protocol 'Family' Specification
	Author(s)	: E. Terrell
	Filename	: draft-terrell-iptx-dhcp-req-iptx-ip-
	Pages		: 18
	Date		: 23-May-02
This document defines the changes when the IP Bit Mapped Header Size
Specification Equals 64 Bits, as would be required for the Implementation Dynamic Host Configuration Protocol (DHCP) to support hosts defined by the IPtX IP Addressing Protocol Family Specification. Furthermore, while the underlining implications regarding any Change in the Header Size Specification maintains the possibility of having a Profound Cascading Affect upon other Protocols. Noting specifically, the affects upon the 'TCP' and 'UDP' Headers, and the corresponding affects upon the Growth in the Number of Available 'PORTS'. Nevertheless, while there is a noticeable growth occurring in each of these areas, they remain manageable, because the difference between the IPv4 and the IPtX Specification is minimal. In which case, it should be clearly understood, the Operations presently defined for the IPv4 IP Addressing System would be the same under the IPt1 Specification. And this is valid because the differences between their IP Addressing Schematic Design does not mandate !
 a requirement for any change, and they both use the same 32Bit Header Size Specification.
In other words, the implementation of the IPtX Specification has little or No affect, nor does it constitute an appreciable change in the Dynamic Host Configuration Protocol Specification, which is Currently used in the IPv4 IP Addressing System. Hence, this work should only be considered as an extension of the RFC(s) governing and supporting the Dynamic Host Configuration Protocol (DHCP) for the IPv4 Specification, because the only objective this paper maintains, is the development and presentation of the IPtX DHCP Specification, which only compliments the requirements in the current RFC(s) defining the DHCP Protocol Specification.

A URL for this Internet-Draft is:

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-terrell-iptx-dhcp-req-iptx-ip-add-spec-00.txt".

A list of Internet-Drafts directories can be found in
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
In the body type:
	"FILE /internet-drafts/draft-terrell-iptx-dhcp-req-iptx-ip-add-spec-00.txt".
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the