V5UA: Query reg Text formatted interface identifier

"Saurabh Jain" <[email protected]>
Newsgroups gmane.ietf.sigtran
Message-ID <[email protected]>
Hi,

I have a query regarding Text formatted interface identifier.
In RFC 3807: V5UA ,    Section 4.2.  V5 Naming Conventions for
Interface Identifier   states :

   If used, the text formatted interface identifier SHALL be coded as
   the hex representation of the integer formatted interface identifier,
   written as a variable length string.


Format for Integar Based Interface Identifier
    0                   1                   2                   3
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Tag (0x1)           |             Length            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |        Link Identifier                              | Chnl ID |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Format for Text Based Interface Identifier
    0                   1                   2                   3
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |           Tag (0x3)           |             Length            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   /                   Interface Identifier (text)                 \
   \                   (Link Identifier + Chnl ID)                 /
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


Example:  	Link Identifier = 3
		Chnl ID = 15

Integer-based Interface Identifier would be coded as
	Binary:	(0000000000000001 0000000000001000)
		(000000000000000000000000011 01111)
	Hex:	00 01 00 08	
		00 00 00 6F		

Question is : What would be the corresponding encoding for Text-based
Interface Identifier?

rgds
Saurabh
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.