List Info

Thread: San Diego meeting slot




San Diego meeting slot
user name
2006-10-03 04:08:12
We have a *tentative* slot assignment for Wednesday
1520-1720.  Agenda
items will follow shortly.

		--Steven M. Bellovin, http://www.cs.columbi
a.edu/~smb

_______________________________________________
Ipr-wg mailing list
Ipr-wgietf.org
https:/
/www1.ietf.org/mailman/listinfo/ipr-wg
San Diego meeting slot
user name
2006-10-04 09:26:01
Steven M. Bellovin wrote:
> We have a *tentative* slot assignment for Wednesday
1520-1720.  Agenda
> items will follow shortly.
Note that we expect a major agenda item to be the revision
of 
draft-ietf-ipr-outbound-rights, which has been submitted to
the I-D 
repository, but not yet published.

                 Harald


_______________________________________________
Ipr-wg mailing list
Ipr-wgietf.org
https:/
/www1.ietf.org/mailman/listinfo/ipr-wg
San Diego meeting slot
user name
2006-10-04 10:11:53
It would be useful to have the WG discuss whether it wish to
adopt:

http://www.ietf.org/internet-drafts/draft-
josefsson-ipr-notices-00.txt

Pending a more clear view of the IETF consensus on that
issue, RFC
3548bis (RFC4648) is somewhat stuck in AUTH48.

The running code seems to differ from the policy here.

Thanks,
Simon

_______________________________________________
Ipr-wg mailing list
Ipr-wgietf.org
https:/
/www1.ietf.org/mailman/listinfo/ipr-wg
San Diego meeting slot
user name
2006-10-04 18:45:13
At 12:11 PM +0200 10/4/06, Simon Josefsson wrote:
>It would be useful to have the WG discuss whether it
wish to adopt:
>
>http://www.ietf.org/internet-drafts/draft-
josefsson-ipr-notices-00.txt
>
>Pending a more clear view of the IETF consensus on that
issue, RFC
>3548bis (RFC4648) is somewhat stuck in AUTH48.
>
>The running code seems to differ from the policy here.
>
>Thanks,
>Simon

I agree with Simon's request, and I'd actually like to see
if we can get
close to WG agreement on a way forward.  If we cannot, the
only way
to get the full functionality of 3548bis is going to be
remove the LGPL-ed
code and replace it with a pointer to a non-RFC place where
it is maintained.
That has a list of problems we're all familiar with, and I'd
rather get clear
answers to the base problem.
			thanks,
				Ted

_______________________________________________
Ipr-wg mailing list
Ipr-wgietf.org
https:/
/www1.ietf.org/mailman/listinfo/ipr-wg
[1-4]

about | contact  Other archives ( Real Estate discussion Medical topics )