Hi,
On 2022-4-29, at 13:54, Lars Eggert wrote:
> the IESG is reviewing what has happened.
the IESG discussed this issue. Below is my personal attempt to summarize the
outcome of this discussion.
We believe that it is permissible under the current rules to include sections
of text that others
Hi,
Adding the Trustees.
Speaking as one of the Trustees but not necessarily for the IETF Trust, I don't
think the IETF Trust has anything to do here. The IETF may.
What I write INLINE below is written as an analysis of the situation from an
IETF Trustees viewpoint, and a legalistic viewpoint
In line:
On 5/1/2022 1:41 PM, John Levine wrote:
It appears that Mukund Sivaraman said:
Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved.
By way of this, by removing the names of authors, isn't the copyright
notice attributed to the
It appears that Mukund Sivaraman said:
> Copyright (c) 2022 IETF Trust and the persons identified as the
> document authors. All rights reserved.
>
>By way of this, by removing the names of authors, isn't the copyright
>notice attributed to the (original) document authors also being removed?
Hi Brian
On Sun, May 01, 2022 at 02:11:11PM +1200, Brian E Carpenter wrote:
[snip]
> > The copyright notice on the document says:
> >
> > Copyright (c) 2022 IETF Trust and the persons identified as the
> > document authors. All rights reserved.
> >
> > By way of this, by removing the na
Hi Mukund, two comments below...
On 30-Apr-22 08:27, Mukund Sivaraman wrote:
On Fri, Apr 29, 2022 at 10:05:10PM +0200, Benno Overeinder wrote:
Hi Lars, WG,
On 29/04/2022 12:54, Lars Eggert wrote:
On 2022-4-29, at 0:30, Cindy Morgan wrote:
The rest of this is a bit of a tangle, and I've refe
On Fri, Apr 29, 2022 at 10:54:13PM +0200, Benno Overeinder wrote:
> Mukund,
>
> On 29/04/2022 22:27, Mukund Sivaraman wrote:
> > >
> > > This is indeed how the DNSOP chairs see it and have guided the (new set
> > > of)
> > > authors in this way. We have also asked Haisheng to contact the
> > >
Mukund,
On 29/04/2022 22:27, Mukund Sivaraman wrote:
This is indeed how the DNSOP chairs see it and have guided the (new set of)
authors in this way. We have also asked Haisheng to contact the secretariat
to correct the situation as we cannot withdraw individual drafts or change
status.
With
On Fri, Apr 29, 2022 at 10:05:10PM +0200, Benno Overeinder wrote:
> Hi Lars, WG,
>
> On 29/04/2022 12:54, Lars Eggert wrote:
> > On 2022-4-29, at 0:30, Cindy Morgan wrote:
> > > The rest of this is a bit of a tangle, and I've referred it to the IESG
> > > for further guidance on what steps the S
Hi Lars, WG,
On 29/04/2022 12:54, Lars Eggert wrote:
On 2022-4-29, at 0:30, Cindy Morgan wrote:
The rest of this is a bit of a tangle, and I've referred it to the IESG for
further guidance on what steps the Secretariat should take next.
the IESG is reviewing what has happened.
(My personal
Hi， Mukund, This is Johnson， I'm very sorry to cause you so much trouble. I think the draft of draft-muks-dns-message-fragments that you submitted to the IETF is quite interesting and shows the importance of dns packet fragmentation in the DNS q
Hi,
On 2022-4-29, at 0:30, Cindy Morgan wrote:
> The rest of this is a bit of a tangle, and I've referred it to the IESG for
> further guidance on what steps the Secretariat should take next.
the IESG is reviewing what has happened.
(My personal first impression is that this might be a case wh
Hi Haisheng Yu / Johnson
On Fri, Apr 29, 2022 at 11:05:34AM +0800, Haisheng Yu wrote:
>Hi， Mukund,
> This is Johnson， I'm very sorry to cause you so much trouble.
>
> I think the draft of draft-muks-dns-message-fragments that you
>submitted to the IETF is quite int
Hi Cindy
On Thu, Apr 28, 2022 at 02:30:07PM -0700, Cindy Morgan wrote:
> Hi Mukand,
>
> When the Secretariat got the request to review the replacement
> relationship suggested by haisheng yu, I checked and saw that
> "haisheng yu" was listed as an author on both
> draft-hsyu-message-fragments and
Hi Mukand,
When the Secretariat got the request to review the replacement relationship
suggested by haisheng yu, I checked and saw that "haisheng yu" was listed as an
author on both draft-hsyu-message-fragments and
draft-muks-dnsop-message-fragments, and so I approved the replaced-by
informati
There was
https://datatracker.ietf.org/doc/html/draft-carpenter-whats-an-author-02
My hope is to revive that draft as an RFC Editor policy issue once the RSWG is
established, because it's broader than just an IETF issue.
Regards
Brian Carpenter
On 29-Apr-22 06:16, Donald Eastlake wrote:
Wh
Hi Donald
On Thu, Apr 28, 2022 at 02:16:16PM -0400, Donald Eastlake wrote:
> What you describe is completely improper but I'm not sure it's exactly
> accurate. When you said you were "removed" as an author, I assumed that a
> new revision of a draft was posted where you were a first page author fo
What you describe is completely improper but I'm not sure it's exactly
accurate. When you said you were "removed" as an author, I assumed that a
new revision of a draft was posted where you were a first page author for
version N but not listed as an author for version N+1. That would also be
improp
On Thu, Apr 28, 2022 at 09:33:08AM -0700, DraftTracker Mail System wrote:
>
> Please DO NOT reply to this email.
>
> I-D:
> Datatracker URL:
> https://datatracker.ietf.org/doc/draft-hsyu-message-fragments/
>
> This document now replaces draft-muks-dnsop-message-fragments
> draft-hsyu-dnsop
19 matches
Mail list logo
