[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [OPSAWG] [Technical Errata Reported] RFC5676 (1928)
- To: "ah at TR-Sys.de" <ah at TR-Sys.de>
- Subject: Re: [OPSAWG] [Technical Errata Reported] RFC5676 (1928)
- From: Juergen Schoenwaelder <j.schoenwaelder at jacobs-university.de>
- Date: Wed, 28 Oct 2009 16:54:23 +0100
- Cc: "akarmaka at cisco.com" <akarmaka at cisco.com>, "opsawg at ietf.org" <opsawg at ietf.org>
- Delivered-to: opsawg at core3.amsl.com
- In-reply-to: <200910281148.MAA03161 at TR-Sys.de>
- List-archive: <http://www.ietf.org/mail-archive/web/opsawg>
- List-help: <mailto:opsawg-request@ietf.org?subject=help>
- List-id: OPSA Working Group Mail List <opsawg.ietf.org>
- List-post: <mailto:opsawg@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
- Mail-followup-to: "ah at TR-Sys.de" <ah at TR-Sys.de>, "alex at cisco.com" <alex at cisco.com>, "akarmaka at cisco.com" <akarmaka at cisco.com>, "dromasca at avaya.com" <dromasca at avaya.com>, "rbonica at juniper.net" <rbonica at juniper.net>, "sob at harvard.edu" <sob at harvard.edu>, "ted.a.seely at sprint.com" <ted.a.seely at sprint.com>, "opsawg at ietf.org" <opsawg at ietf.org>
- References: <20091028110044.GA19229 at elstar.local> <200910281148.MAA03161 at TR-Sys.de>
- Reply-to: Juergen Schoenwaelder <j.schoenwaelder at jacobs-university.de>
- User-agent: Mutt/1.5.20 (2009-06-14)
On Wed, Oct 28, 2009 at 12:48:02PM +0100, ah at TR-Sys.de wrote:
> > Hm. The text you quote is the definition of 'd' for INTEGER typed
> > DISPLAY-HINTs. Given the absence of a definition of 'd' for OCTET
> > STRING types DISPLAY-HINTs, it is not really clear what RFC 2579
> > intended. ...
>
> The text in RFC 2579 for numerical translations is convoluted indeed,
> but I believe it is unambiguous.
> It starts out with "For INTEGER types ..." and continues with:
> "For all types, ..." as quoted above.
See, it depends how you parse the text. One can read it as the initial
"for INTEGER types" phrase qualifies the whole paragraph for INTEGER
types. I have to look at code I wrote many years ago to see what my
implementation does. Knowing what implementations do would certainly
help.
/js
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany
Fax: +49 421 200 3103 <http://www.jacobs-university.de/>