RFC 1706 Compliance in BIND 8.2.3?

[Joseph Caldwell]

Is BIND 8.2.3 supposed to be compliant with RFC 1706 for NSAP
RR types?  Specifically, the RFC describes being able to use
special 0x characters in the master file.

When I use 0x, my BIND 8.2.3 server rejects it.
Example (straight from the RFC):
infidel IN NSAP 0x47.0005.80.005a00.0000.0001.e133.ffffff000164.00

causes the following error msg:
23-Mar-2001 16:29:16.975 load: notice: STATICDNS.TESTNET.DB:10: NSAP RR
error near (0x47.0005.80.005a00.0000.0001.e133.ffffff000164.00)

Looking at the inet_nsap_addr() function in lib/inet/nsap_addr.c
(which is where the RR is validated, correct?), I don't see any
allowance for parsing the 0x.  If I change the x to some valid hex
character, then I don't get the error.

Since I have ported the code to a new operating system (OS/400),
I just want to make sure this wasn't a porting problem on my part.

Thanks in advance for your help.
Joe
-------------------------------------------------------------
Joe Caldwell, IBM Corp., iSeries 400 Laboratory
1701 North St., Dept GZVA, Endicott, N.Y. 13760
Internet e-mail: joecwell at us.ibm.com
-------------------------------------------------------------