Re: Document Action: 'Integrity, privacy and security in OPES for SMTP' to Informational RFC

jfc,

my understanding is that the mailing list will remain open for further 
discussions etc.

Ted - could you please let us know if this assumption is not correct.

Thanks,
   Markus

jfcm wrote:
> 
> Thank you to the Chairs and ADs. A clear IAB analysis, a clearly 
> understood charter, dedicated authors and open minded members. Thanks to 
> everyone.
> 
> May I suggest that we continue relating on OPES in the following 
> context. Since the beginning my interest is in the support of the DNS to 
> be able to massage DNS requests and responses in order to support ML.ML, 
> Classes, DDDS relations, etc.  without modifying the ends. Also, in what 
> I call the ONES (Open Networked Extended Services), that is to say 
> specialized networks of call-out servers.
> 
> I think that the debated Multi-Level addressing and the Multitopology 
> approaches enter into that category. OPES could help the transition to, 
> a good location for OPES being for example NATs, helping reducing 
> progressively their specificities and transitioning to IPv6 or 
> multi-IPvX. I think also that OPES could be a very simple way to get 
> adjencies information and manage routing through meshed or distributed 
> supervisory functions. Their role in multilingualisation (localisation 
> of the globalisation, globalisation=internationalisation of the medium + 
> localisation of the end) can also be important.
> 
> It could be great to have a site for assembling the links on OPES 
> issues. I am considering a site with an African R&D center to that end 
> and MoUs with various SSDOs and Academic institutions. There would be 
> the RFCs, the texts and the open source software you could give us 
> access to.
> 
> Question: can I cite this mailing list (can people still register and 
> access archives?).
> jfc
> 
> 
> 
> 
> At 12:40 13/03/2007, Tony Hansen wrote:
>> Thanks to everyone in the OPES WG for your work in getting this document
>> put to bed.
>>
>> This concludes the chartered work of the Working Group. Anyone who
>> wishes to carry on the work of the WG is encouraged to do so using
>> individual submissions. The mailing list will remain open and available
>> for anyone to use to discuss such individual internet drafts.
>>
>> Thanks again to everyone for the fine work that's been accomplished over
>> these past many years:
>>
>>   RFC 3752  2002-08  OPES Use Cases and Deployment Scenarios
>>   RFC 3835  2002-12  An Architecture for OPES
>>   RFC 3836  2002-12  Requirements for OPES Callout Protocols
>>   RFC 3837  2003-12  Security Threats and Risks for OPES
>>   RFC 3838  2004-04  Policy, Authorization & Enforcement Req'ts of OPES
>>   RFC 3897  2004-05  OPES entities and end points communication
>>   RFC 3914  2004-04  OPES Treatment of IAB Considerations
>>   RFC 4037  2004-05  OPES Callout Protocol (OCP) Core
>>   RFC 4236  2005-11  HTTP Adaptation with OPES
>>   RFC 4496  2006-01  OPES SMTP Use Cases
>>   RFC ????  2007-02  Integrity, privacy and security in OPES for SMTP
>>
>> Your OPES co-chairs,
>>
>>         Markus Hofmann & Tony Hansen
>>
>> The IESG wrote:
>> > The IESG has approved the following document:
>> >
>> > - 'Integrity, privacy and security in OPES for SMTP '
>> >    <draft-ietf-opes-smtp-security-03.txt> as an Informational RFC
>> >
>> > This document is the product of the Open Pluggable Edge Services 
>> Working
>> > Group.
>