RE: SCMP Informational Draft?
"Phillip M Hallam-Baker" <[email protected]> Fri, 4 Jun 1999 10:11:23 -0400
| Newsgroups | gmane.ietf.scmp |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. ------=_NextPart_000_0003_01BEAE72.998B4AA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit In the old days [TM] a Request for Comments was just that. The sooner information is presented in a permanent record, the better. Not least because the priority dates for patent prior are are set. If people are building code to a spec it is better that there be a fixed target than we wait for perfection. The only case in which an 'informational' RFC poses a problem is when the informational route is chosen as a means of importing 'proprietary' technology into IETF process which is not the case here. There is no shortage of RFC numbers! ------=_NextPart_000_0003_01BEAE72.998B4AA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"> <HTML> <HEAD> <META content=3D"text/html; charset=3Diso-8859-1" = http-equiv=3DContent-Type> <META content=3D'"MSHTML 4.72.3110.7"' name=3DGENERATOR> </HEAD> <BODY> <DIV><SPAN class=3D940410014-04061999><FONT color=3D#0000ff face=3DArial = size=3D2>In the=20 old days [TM] a Request for Comments was just that.</FONT></SPAN></DIV> <DIV><SPAN class=3D940410014-04061999><FONT color=3D#0000ff face=3DArial = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D940410014-04061999><FONT color=3D#0000ff face=3DArial = size=3D2>The=20 sooner information is presented in a permanent record, the better. Not = least=20 because the priority dates for patent prior are are set. If people are = building=20 code to a spec it is better that there be a fixed target than we wait = for=20 perfection.</FONT></SPAN></DIV> <DIV><SPAN class=3D940410014-04061999><FONT color=3D#0000ff face=3DArial = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D940410014-04061999><FONT color=3D#0000ff face=3DArial = size=3D2>The=20 only case in which an 'informational' RFC poses a problem is when the=20 informational route is chosen as a means of importing 'proprietary' = technology=20 into IETF process which is not the case here.</FONT></SPAN></DIV> <DIV><SPAN class=3D940410014-04061999><FONT color=3D#0000ff face=3DArial = size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D940410014-04061999><FONT color=3D#0000ff face=3DArial = size=3D2>There=20 is no shortage of RFC numbers!</FONT></SPAN></DIV></BODY></HTML> ------=_NextPart_000_0003_01BEAE72.998B4AA0--