Howard posted a link about a draft RFC tat was addressing the future of RFC 1700. We had a back and forth exchange about the utility of this RFC, and I made mention of a couple of improvements that could be made. I decided to go ahead and put my two cents worth on the matter and I submitted my comments to the RFC editor. Basically, my comments were in two areas. One was that RFC 1700, and its successor RFCs, need to remain in ASCII format for its portability, particularly in places like wiring closets, etc, where an Internet connection is not available. Additionally, my comments regarding indication of the predominant transport layer protocol in use were also submitted. We need to have a ready identifier that either TCP or UDP is in use for a given application. I actually got a reply from Bob Braden, the RFC editor. He has passed my comments on to IANA for consideration. He took my comments and made an additional proposal which is an outstanding idea. He felt there was nothing that could prevent a daily updated RFC 1700 that could be built with a programming script. In essence, RFC 1700 would remain in ASCII format and stay current every day. I hope that happens. v/r, Paul Werner > Every so often someone asks about port numbers and IP protocol numbers > and > other such numbers and we all moan and groan about the demise of RFC > 1700, > the Assigned Numbers RFC. > > Well, guess what I just discovered? The Internet Assigned Numbers > Authority > (IANA) is still alive and doing well and they keep some nice documents > with > this sort of information. You may want to bookmark this URL: > > http://www.iana.org/numbers.html ________________________________________________ Get your own "800" number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=19424&t=19350 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
