Hi folks,
it seems that we are drawing close to a consensus here:
- Access to data that the IETF has created and needs to function is a
paramount basic principle. Not to be compromised. So it needs to go VERY
plainly into section 2.2 principles.
- Access to software is a very-nice-to-have, but
Scott Bradner wrote:
Harald sez:
if decisions of the IAOC can be appealed rather reads:
--
If someone believes that the IAOC has violated the IAOC rules and
procedures, he or she can ask the IETF leadership to investigate the
Harald Tveit Alvestrand wrote:
--On 3. desember 2004 11:24 +0100 Brian E Carpenter [EMAIL PROTECTED]
wrote:
The variance clause that I suggested has been inserted in section 5
on funding. I think it should apply more generally, and should
be placed as the second paragraph of section 3, slightly
--On mandag, desember 06, 2004 10:39:27 +0100 Brian E Carpenter
[EMAIL PROTECTED] wrote:
Scott Bradner wrote:
Harald sez:
if decisions of the IAOC can be appealed rather reads:
--
If someone believes that the IAOC has violated the
Harald Tveit Alvestrand wrote:
Hi folks,
it seems that we are drawing close to a consensus here:
- Access to data that the IETF has created and needs to function is a
paramount basic principle. Not to be compromised. So it needs to go VERY
plainly into section 2.2 principles.
- Access to
Kindly me from the list
would be appreicated
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
Harald Tveit Alvestrand
Sent: Monday, December 06, 2004 3:27 PM
To: Brian E Carpenter; Scott Bradner
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re:
on 2004-12-06 10:29 am Harald Tveit Alvestrand said the following:
...
Replace the current section from 2.2 that says:
6. The right to use any intellectual property rights created by any
IASA-related or IETF activity may not be withheld or limited in
any way by ISOC from
Kindly unscribe me from the list
would be appreicated
Thanks
-Raghuveer
--
** This email is confidential and is intended for the original recipient(s)
only. If you have erroneously received this mail, please delete it immediately
and notify the sender. Unauthorized copying, disclosure or
I agree with what you are trying to say, but I'm not sure about this
wording:
The IAD is responsible for ensuring that all contracts give the IASA
and the IETF the rights in data that is needed to satisfy the principle
of data access.
Maybe:
The IAD is responsible for ensuring that all
6. The IASA, on behalf of the IETF, shall have an irrevocable,
permanent right of access and later use to all data created
in support of the IETF's activities, including
the right to disclose it to other parties of its choosing.
...
Reasonable, but I want to be
Margaret Wasserman wrote:
I agree with what you are trying to say, but I'm not sure about this
wording:
The IAD is responsible for ensuring that all contracts give the IASA
and the IETF the rights in data that is needed to satisfy the principle
of data access.
Maybe:
The IAD is responsible
--On mandag, desember 06, 2004 13:25:31 +0100 Brian E Carpenter
[EMAIL PROTECTED] wrote:
Margaret Wasserman wrote:
I agree with what you are trying to say, but I'm not sure about this
wording:
The IAD is responsible for ensuring that all contracts give the IASA
and the IETF the rights in data
On Mon, Dec 06, 2004 07:00:32AM -0500, Margaret Wasserman allegedly wrote:
I agree with what you are trying to say, but I'm not sure about this
wording:
The IAD is responsible for ensuring that all contracts give the IASA
and the IETF the rights in data that is needed to satisfy the
After reviewing the discussion on this topic, I think the rough consensus
is conformant with this suggestion:
- Remove the 2nd (Disclaimer:) paragraph from section 5
- Insert the following as part of section 3 (I suggest just before section
3.1):
If the IASA is unable to comply with the
Harald suggests:
- Remove the 2nd (Disclaimer:) paragraph from section 5
- Insert the following as part of section 3 (I suggest just before section
3.1):
If the IASA is unable to comply with the procedures described in this
document for legal, accounting or practical reasons, the IAOC
HiRajat,
as per my knowledge,as of now the application that are expecting XML type encoding method for Msg Body are still at draft level (Video control commands, Conferencing). so the application built on the stack has to take care of these things.
Rajesh.Kalagarla
---Original
Scott Bradner wrote:
Harald suggests:
- Remove the 2nd (Disclaimer:) paragraph from section 5
- Insert the following as part of section 3 (I suggest just before section
3.1):
If the IASA is unable to comply with the procedures described in this
document for legal, accounting or practical
Howdy,
In-line...
Wijnen, Bert (Bert) wrote:
Inline
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
Brian E Carpenter
Sent: Friday, December 03, 2004 11:33
To: [EMAIL PROTECTED]
Subject: iasa-bcp-01 - ISOC support
7. ISOC Responsibilities for IASA
...
After a brief trip to the lawyer, and considering current discussion... a
new suggestion:
Replace principle 6 with the following:
6. The IETF, through the IASA, shall have a perpetual
right to use, display, distribute, reproduce, modify and
create derivatives of all data created
on 2004-12-06 10:36 pm Harald Tveit Alvestrand said the following:
After a brief trip to the lawyer, and considering current discussion... a
new suggestion:
Replace principle 6 with the following:
6. The IETF, through the IASA, shall have a perpetual
right to use, display,
Harald writes:
Brian,
I don't think irrevocably assigned to the IETF works well for money.
In all other cases, money going to support the IETF is called
credited to the IASA account.
In section 5, section 5.2 and 5.3 talk about money credited to the IASA
account. I'd rather add a
Done
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
Harald Tveit Alvestrand
Sent: Monday, December 06, 2004 10:20
To: [EMAIL PROTECTED]
Subject: Consensus? Variance
After reviewing the discussion on this topic, I think the
rough consensus
is
Changed text as suggested by Leslie.
I had re-send my request for inpout while on the plane.
I have now seen both Leslies and Margarets responses.
Thanks,
Bert
-Original Message-
From: Leslie Daigle [mailto:[EMAIL PROTECTED]
Sent: Monday, December 06, 2004 14:41
To: Wijnen, Bert
In line
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
Harald Tveit Alvestrand
Sent: Monday, December 06, 2004 16:36
To: [EMAIL PROTECTED]
Subject: Consensus(2)? IPR rights and all that
After a brief trip to the lawyer, and considering current
Harald,
I am enroute back to Washington at the moment, but did want to comment on
IP matters.
I think it fair to state in the document what the IETF thinks appropriate
for it to manage its own affairs going forward, but one of the matters we
will have to work out is the fact that there is
At 03:41 07/12/2004, Bob Kahn wrote:
Harald,
I am enroute back to Washington at the moment, but did want to comment on
IP matters.
I think it fair to state in the document what the IETF thinks appropriate
for it to manage its own affairs going forward, but one of the matters we
will have to
--On tirsdag, desember 07, 2004 02:20:38 +0100 Wijnen, Bert (Bert)
[EMAIL PROTECTED] wrote:
After a brief trip to the lawyer, and considering current
discussion... a new suggestion:
Replace principle 6 with the following:
6. The IETF, through the IASA, shall have a perpetual
right to
Dr. Kahn,
I am sure that if we so desire, we can keep laywers entertained for several
years sorting out the ownership of reserves, data and systems created using
funds from IETF meeting fees. But we should not allow this potential for
trouble prevent us from making a clear picture of what we
The IESG has approved the following document:
- 'RTP Payload for Text Conversation '
draft-ietf-avt-rfc2793bis-09.txt as a Proposed Standard
This document is the product of the Audio/Video Transport Working Group.
The IESG contact persons are Allison Mankin and Jon Peterson.
Technical
The IESG has approved the following document:
- 'Simple Network Time Protocol Configuration Option for DHCPv6 '
draft-ietf-dhc-dhcpv6-opt-sntp-01.txt as a Proposed Standard
This document is the product of the Dynamic Host Configuration Working Group.
The IESG contact persons are Margaret
The IESG has approved the following document:
- 'Management Information Base for the User Datagram Protocol (UDP) '
draft-ietf-ipv6-rfc2013-update-04.txt as a Proposed Standard
This document is the product of the IP Version 6 Working Group Working Group.
The publication of this document
31 matches
Mail list logo
