Hector Santos wrote:
One initial and obvious design consideration is length limit related. One
reviewer did suggest some 'include' concept or protocol to access large
list.
I'd venture to say that "include" ala SPF is specific NON-REQUIREMENT,
as it violates the requirement that the query op
On Fri, Jul 28, 2006 at 08:01:18AM -0700, Michael Thomas allegedly wrote:
> Hector Santos wrote:
>
> >One initial and obvious design consideration is length limit related. One
> >reviewer did suggest some 'include' concept or protocol to access large
> >list.
> >
> >
> I'd venture to say that "in
t; <[EMAIL PROTECTED]>
To:
Sent: Friday, July 28, 2006 11:32 AM
Subject: Re: [ietf-dkim] include
> > I'd venture to say that "include" ala SPF is specific NON-REQUIREMENT,
> > as it violates the requirement that the query operation provide a
> > deterministic
>
Mark Delany wrote:
On Fri, Jul 28, 2006 at 08:01:18AM -0700, Michael Thomas allegedly wrote:
Hector Santos wrote:
One initial and obvious design consideration is length limit related. One
reviewer did suggest some 'include' concept or protocol to access large
list.
I'd ventu
On Fri, Jul 28, 2006 at 09:18:35AM -0700, Michael Thomas allegedly wrote:
> Perhaps a better mechanism is to just completely disallow jumps from
> one domain namespace to another, ie that any indirection must take place
> in the subtree of the consulted domain, and that it's just, say, an n stage
On Jul 28, 2006, at 9:13 AM, Hector Santos wrote:
The allow list was added primarily recognizing it as a requirement
understanding it would be one of the design issues to work out.
A list of designated signing domains would be indicative of a small
outfit. Larger organizations should have
