SORT BY:

LIST ORDER
THREAD
AUTHOR
SUBJECT


SEARCH

IPS HOME


    [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

    RE: iSCSI: CHAP_C Encoding


    • To: "Paul Koning" <pkoning@equallogic.com>
    • Subject: RE: iSCSI: CHAP_C Encoding
    • From: "Lakshmi Ramasubramanian" <nramas@windows.microsoft.com>
    • Date: Mon, 16 Jun 2003 12:04:51 -0700
    • Cc: <ips@ece.cmu.edu>
    • Content-class: urn:content-classes:message
    • Content-Transfer-Encoding: quoted-printable
    • Content-Type: text/plain;charset="us-ascii"
    • Delivered-To: ips@ece.cmu.edu
    • Sender: owner-ips@ece.cmu.edu
    • Thread-Index: AcM0Oa8yVneBMjE9T7GjKhmUz/U1vgAAEZow
    • Thread-Topic: iSCSI: CHAP_C Encoding

    In that case Section 11.1.4 should state that CHAP_C is a large binary
    value (which'll then eliminate the use of Decimal encoding for CHAP_C).
    Correct?
    
     -lakshmi
    
    -----Original Message-----
    From: Paul Koning [mailto:pkoning@equallogic.com] 
    Sent: Monday, June 16, 2003 12:01 PM
    To: Lakshmi Ramasubramanian
    Cc: ips@ece.cmu.edu
    Subject: Re: iSCSI: CHAP_C Encoding
    
    >>>>> "Lakshmi" == Lakshmi Ramasubramanian
    <nramas@windows.microsoft.com> writes:
    
     Lakshmi> Section 11.1.4 states that CHAP_C is a binary value, and
     Lakshmi> hence could be a regular binary value ( <= 64 bits) or a
     Lakshmi> large binary value ( > 64 bits) (Section 5.1 Text
     Lakshmi> Format). So CHAP_C can be encoded in decimal format
     Lakshmi> also. Right? (Decimal format is allowed only for regular
     Lakshmi> binary values).
    
    No, because the length matters, and decimal numbers don't have a
    length you can derive from the encoding.
    
           paul
    
    
    
    


Home

Last updated: Mon Jun 16 17:19:24 2003
12641 messages in chronological order