John, Brian
Most standards organizations require that participants who have, or whose
company has, IPR relevant to a potential standard, disclose this at an early
stage and at least prior to publication.
The participants in the IETF are individuals however RFC3979 addresses this
by stating that
On 17/09/2013 05:34, Alan Clark wrote:
...
It should be noted that the duty to disclose IPR is NOT ONLY for the authors
of a draft, and the IETF reminder system seems to be focused solely on
authors. The duty to disclose IPR lies with any individual or company that
participates in the IETF not
On 09/16/2013 08:03 PM, Gonzalo Camarillo wrote:
Hi Glen,
as I mentioned in another email, that question is just a reminder.
No, it's not. It is a roadblock. If it was just a reminder. I would
be free to ignore it, in the same way that I ignore a reminder from my
calendar about a meeting
--On Thursday, September 19, 2013 07:57 +1200 Brian E Carpenter
brian.e.carpen...@gmail.com wrote:
On 17/09/2013 05:34, Alan Clark wrote:
...
It should be noted that the duty to disclose IPR is NOT ONLY
for the authors of a draft, and the IETF reminder system
seems to be focused solely on
--On Wednesday, September 18, 2013 17:22 -0400 Alan Clark
alan.d.cl...@telchemy.com wrote:
John, Brian
Most standards organizations require that participants who
have, or whose company has, IPR relevant to a potential
standard, disclose this at an early stage and at least prior
to
From 29 years experience in ATIS, CCITT, CEPT, ETSI, IETF, ITU, TIA and
other standards organizations and extensive experience with standards that
do have associated IPR it is apparent that asking for confirmation at
multiple points in the standards development process IS necessary.
For example:
Message-
From: Qin Wu [mailto:bill...@huawei.com]
Sent: Saturday, September 14, 2013 8:45 AM
To: Glen Zorn
Cc: Romascanu, Dan (Dan); draft-ietf-xrblock-rtcp-xr-
qoe@tools.ietf.org
Subject: RE: IPR Disclosures for draft-ietf-xrblock-rtcp-xr-qoe
Hi,Glen:
Would you like to not bother IESG
@tools.ietf.org
Subject: RE: IPR Disclosures for draft-ietf-xrblock-rtcp-xr-qoe
Hi,Glen:
Would you like to not bother IESG to make confirmation?
I am a little confused with what you sent.
What's wrong with the IETF IPR policy?
Your blame on this doesn't help solve the problem.
Regards!
-Qin
@tools.ietf.org; Shida Schubert; rai-...@tools.ietf.org; The
IESG; ietf@ietf.org
Subject: Re: IPR Disclosures for draft-ietf-xrblock-rtcp-xr-qoe
Hi Glen,
as I mentioned in another email, that question is just a reminder. In
the past, it has happened that even long-time IETF participants
On 09/16/2013 02:20 PM, Romascanu, Dan (Dan) wrote:
I have doubts myself, doubts that I shared with the IESG that this
question is really needed. Asking this question at the end of the
process after the conformance with BCP 78 and BCP 79 was explicitly
declared with each version of the I-D
; Qin
Wu
Subject: Re: IPR Disclosures for draft-ietf-xrblock-rtcp-xr-qoe
Hi Glen,
as I mentioned in another email, that question is just a reminder. In
the past, it has happened that even long-time IETF participants with a
lot of experience had forgotten about a particular disclosure until
can we try to keep life simple? it is prudent to check what (new)
ipr exists for a draft at the point where the iesg is gonna start
the sausage machine to get it to rfc. if the iesg did not do this,
we would rightly worry that we were open to a submarine job. this
has happened, which is why
--On Monday, September 16, 2013 07:14 -1000 Randy Bush
ra...@psg.com wrote:
can we try to keep life simple? it is prudent to check what
(new) ipr exists for a draft at the point where the iesg is
gonna start the sausage machine to get it to rfc. if the iesg
did not do this, we would
John == John C Klensin john-i...@jck.com writes:
John It seems to me that, in this particular case, too many people
John are assuming a far more rigid process than actually exists or
John can be justified by any IETF consensus procedure. Let's just
John stop that.
I agree with
: Romascanu, Dan (Dan); draft-ietf-xrblock-rtcp-xr-
qoe@tools.ietf.org
Subject: RE: IPR Disclosures for draft-ietf-xrblock-rtcp-xr-qoe
Hi,Glen:
Would you like to not bother IESG to make confirmation?
I am a little confused with what you sent.
What's wrong with the IETF IPR policy?
Your blame
--On Monday, September 16, 2013 19:35 +0700 Glen Zorn
g...@net-zen.net wrote:
...
The wording of this question is not a choice. As WG chairs we
are required to answer the following question which is part
of the Shepherd write-up as per the instructions from the
IESG
On Sep 16, 2013, at 3:51 PM, Ted Lemon ted.le...@nominum.com wrote:
This is a claim in the boilerplate which the IETF, not the authors, are
making.
I am sure flames are already directed my way for being imprecise here, but what
I mean is that although the authors put this boilerplate in the
Ralph,
Will you be in Vancouver? I'd like to get some time to talk about IPSO
and also my new project for the White House - SmartUSA Challenge. I plan to
be there if I can get approval for foreign travel.
Geoff Mulligan
Presidential Innovation Fellow
Cyber-Physical Systems
SmartUSA
On Sep 16, 2013, at 1:37 PM, John C Klensin john-i...@jck.com wrote:
(2) Whether the submitted in full conformance... statement in
I-Ds is sufficient to cover IPR up to the point of posting of
the I-D. If the answer is no, then there is a question of why
we are wasting the bits. If it is
On 17/09/2013 08:10, Ted Lemon wrote:
On Sep 16, 2013, at 3:51 PM, Ted Lemon ted.le...@nominum.com wrote:
This is a claim in the boilerplate which the IETF, not the authors, are
making.
I am sure flames are already directed my way for being imprecise here, but
what I mean is that although
(off-list)
John C Klensin wrote:
The first sentence of the writeup template, As required by RFC
4858, this is the current template... is technically invalid
because RFC 4858, as an Informational document, cannot _require_
anything of the standards process.
I'm OK with asserting that an
On 08/21/2013 09:20 PM, Romascanu, Dan (Dan) wrote:
Dear authors of draft-ietf-xrblock-rtcp-xr-qoe,
Please confirm that any and all appropriate IPR disclosures required for full
conformance with the provisions of BCP 78 and BCP 79 for this document have
already been filed. The confirmation
On 08/21/2013 09:20 PM, Romascanu, Dan (Dan) wrote:
Dear authors of draft-ietf-xrblock-rtcp-xr-qoe,
Network Working Group A. Clark
Internet-Draft Telchemy
Intended status: Standards Track
On 08/21/2013 09:20 PM, Romascanu, Dan (Dan) wrote:
Dear authors of draft-ietf-xrblock-rtcp-xr-qoe,
Please confirm that any and all appropriate IPR disclosures required for full
conformance with the provisions of BCP 78 and BCP 79 for this document have
already been filed. The confirmation
On 08/21/2013 09:20 PM, Romascanu, Dan (Dan) wrote:
Dear authors of draft-ietf-xrblock-rtcp-xr-qoe,
Network Working Group A. Clark
Internet-Draft Telchemy
Intended status: Standards Track
On 08/21/2013 09:20 PM, Romascanu, Dan (Dan) wrote:
Dear authors of draft-ietf-xrblock-rtcp-xr-qoe,
Please confirm that any and all appropriate IPR disclosures required for full
conformance with the provisions of BCP 78 and BCP 79 for this document have
already been filed. The confirmation
26 matches
Mail list logo
