[81417] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Micorsoft's Sender ID Authentication......?

daemon@ATHENA.MIT.EDU (Dave Crocker)
Wed Jun 8 23:40:35 2005

From: Dave Crocker <dhc2@dcrocker.net>
To: <nanog@trapdoor.merit.edu>
Reply-To: Dave Crocker <dcrocker@bbiw.net>
Date: Wed, 8 Jun 2005 20:39:59 -0700
In-Reply-To: <b60e3932a94ce6bcf821d454df64e11d@isipp.com>
X-Songbird-From: dhc2@dcrocker.net
Errors-To: owner-nanog@merit.edu


>  In part the problem was 'legal' (versus technical)...the folks involved
>  in the working list from MS...technical people, offered ongoing
>  reassurance that the as-yet-unpublished patent apps were benign, that

Folks,

For all the reasons already cited in this thread, it's clear that legal 
concerns were a factor.

However the reality is that the IETF working group was not converging on 
consensus and showed no ability to repair this fatal barrier.  The legal 
issues were part of this, but it is far from obvious that fixing the legal 
issues would have gotten a better outcome.

Besides the criticisms of the basic path registration (somewhat akin to 
registering source routes) schemes used by SPF and Sender-ID, those two 
different specs have different constituencies and were not overly 
successful as merging.

  d/
  ---
  Dave Crocker
  Brandenburg InternetWorking
  +1.408.246.8253
  dcrocker  a t ...
  WE'VE MOVED to:  www.bbiw.net



home help back first fref pref prev next nref lref last post