RE: MaxRecvPDULength question

["THALER,PAT (A-Roseville,ex1)" <pat_thaler@agilent.com>]

Martins,

If we are going to rename it, the name should be accurate and clear. I don't think MaxRecvDataLength is clear because there are lots of data lengths involved in the draft. Also, some of the parameters use length and some use size.

MaxRecvDataSegmentSize or
MaxRecvPDUDataSize

would be clear, consistant with other names and accurate. I don't feel strongly about changing the name to improve it but removing the context for which data length is being negotiated would reduce accuracy/clarity of the name.

Regards,
Pat

-----Original Message-----
From: Martins Krikis [mailto:mkrikis@yahoo.com]
Sent: Wednesday, May 22, 2002 12:20 PM
To: ips@ece.cmu.edu
Subject: Re: MaxRecvPDULength question



--- Paul Koning <ni1d@arrl.net> wrote:

> Are you proposing to rename the key so its name is
> "MaxRecvDataLength"?  Yes, that would be more
> accurate, but why bother
> at this point?

Because it would be more accurate!

I personally don't mind changes in the draft that
make it clearer but require me to change one string
constant.

  Martins Krikis, Intel Corp.


__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com