Re: Late comments on the msgtrk documents

: eric> This brings up another point however.  RFC 1891 specifies the ENVID
: eric> value as being 100 characters.  Since we have changed this to
: eric> local-envid "@" fqhn, should we extend this (I claim yes)?  If so, to
: eric> what value?
: 
: Given that RFC 2822 section 4.5.3.1 states that the maximum length of he
: domain portion is 255 characters, I would assume 256 (255 + 1 for "@")
: would be a good number to add.

I was starting to make this change and suddenly realized that we may
have a conundrum here.  The obvious approach is to increase the length
of the ENVID parameter from 100 to 356.  However, how would I implement
this when initially submitting the message?  The obvious implementation
(if the submitter supports MSGTRK) would be to always create a fully
qualified ENVID.  But if that message gets relayed to a non-MSGTRK
agent, that ENVID could be too long, and so you've created a
non-compliant envelope.

I'm starting to lean toward leaving it at 100 characters for this
reason, although that could be problematic (disastrous?) if IDN goes
for ACE encoding, since the expected length of domain names will
go up.

Opinions?

eric