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

*To*: ietf-openpgp@xxxxxxx*Subject*: Re: Critical bits and notations*From*: David Shaw <dshaw@xxxxxxxxxxxxxxx>*Date*: Wed, 11 May 2005 10:35:36 -0400*In-reply-to*: <87psvymdtl.fsf@xxxxxxxxxxxxxxxxxxxxx> <20050511042836.91ACA57EE6@xxxxxxxxxx>*List-archive*: <http://www.imc.org/ietf-openpgp/mail-archive/>*List-id*: <ietf-openpgp.imc.org>*List-unsubscribe*: <mailto:ietf-openpgp-request@imc.org?body=unsubscribe>*Mail-followup-to*: ietf-openpgp@xxxxxxx*Openpgp*: id=99242560; url=http://www.jabberwocky.com/david/keys.asc*References*: <20050511042836.91ACA57EE6@xxxxxxxxxx> <87psvymdtl.fsf@xxxxxxxxxxxxxxxxxxxxx> <20050511042836.91ACA57EE6@xxxxxxxxxx>*Sender*: owner-ietf-openpgp@xxxxxxxxxxxx*User-agent*: Mutt/1.5.8i

On Tue, May 10, 2005 at 09:28:36PM -0700, "Hal Finney" wrote: > > In my opinion, the critical bit on a notation packet should mean > that the implementation needs to recognize that particular notation, > not just notation packets in general. Otherwise we would have no way > of expressing the requirement that the particular notation packet be > understood. That makes good sense, and I agree. However, the text in the draft doesn't exactly say this (and rather implies the opposite). I suggest adding this sentence (or similar) to the end of section 5.2.3.16. Notation Data: When used on a notation subpacket, the critical bit refers to that particular notation, and not to notation subpackets in general. David

**Follow-Ups**:**Re: Critical bits and notations***From:*Jon Callas

**References**:**Re: Critical bits and notations***From:*"Hal Finney"

**Re: Critical bits and notations***From:*Werner Koch

- Prev by Date:
**minor comments on draft-ietf-openpgp-rfc2440bis-12.txt** - Next by Date:
**Re: Tag 11 unclear** - Previous by thread:
**Re: Critical bits and notations** - Next by thread:
**Re: Critical bits and notations** - Index(es):