It is a matter of interpretation. What does BCP stand for within IETF? ;-) But seriously, Best Common Practise, IMHO, means, follow this unless you have a damn good reason not to and if you have that damn good reason then ask for the BCP to be updated. Just my interpretation. Best regards Debbie > -----Original Message----- > From: kre@xxxxxxxxxxxxx [mailto:kre@xxxxxxxxxxxxx] > Sent: 17 June 2008 19:50 > To: debbie@xxxxxxxxxxxxxxxxxx > Cc: iesg@xxxxxxxx; ietf@xxxxxxxx > Subject: Re: Appeal against IESG blocking DISCUSS on > draft-klensin-rfc2821bis > > Date: Tue, 17 Jun 2008 15:50:02 +0100 > From: "Debbie Garside" <debbie@xxxxxxxxxxxxxxxxxx> > Message-ID: <049b01c8d089$6c901ce0$0a00a8c0@CPQ86763045110> > > | I would also add that to go against an IETF BCP > > Huh? The BCP in question says (in a bit more eloquent form) > "Here are some domain names that are reserved from all normal > use, and so are suitable for use in places where something > with the syntax of a valid domain names is required, but no > real domain name should be used - use them where applicable". > > It does not say "you must use these domain names" (for any > purpose at all). > > Where's the "go against an IETF BCP" here? > > kre > > > > > > > _______________________________________________ IETF mailing list IETF@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf