[tcpm] Fwd: Delivery Status Notification (Failure)
Michael Welzl <michawe@ifi.uio.no> Tue, 13 March 2018 13:33 UTC
Return-Path: <michawe@ifi.uio.no>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB6112D942; Tue, 13 Mar 2018 06:33:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cp3qcNN7KOH1; Tue, 13 Mar 2018 06:33:02 -0700 (PDT)
Received: from mail-out02.uio.no (mail-out02.uio.no [IPv6:2001:700:100:8210::71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA164127337; Tue, 13 Mar 2018 06:33:01 -0700 (PDT)
Received: from mail-mx06.uio.no ([129.240.10.40]) by mail-out02.uio.no with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from <michawe@ifi.uio.no>) id 1evk31-0008ld-HU; Tue, 13 Mar 2018 14:32:59 +0100
Received: from [160.80.82.29] by mail-mx06.uio.no with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) user michawe (Exim 4.90_1) (envelope-from <michawe@ifi.uio.no>) id 1evk2v-0000j3-PG; Tue, 13 Mar 2018 14:32:59 +0100
From: Michael Welzl <michawe@ifi.uio.no>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E667FC21-BAAE-4E00-AD7D-81534BF97867"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <F02F79EC-F63E-43F2-92B4-3D8DC234D86E@ifi.uio.no>
References: <5aa7bff2.89122e0a.62f45.0ddd.GMRIR@mx.google.com>
To: "tcpm-chairs@ietf.org" <tcpm@ietf.org>, tsvwg-chairs@ietf.org
Date: Tue, 13 Mar 2018 14:32:51 +0100
X-Mailer: Apple Mail (2.3273)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx06.uio.no: 160.80.82.29 is neither permitted nor denied by domain of ifi.uio.no) client-ip=160.80.82.29; envelope-from=michawe@ifi.uio.no; helo=[160.80.82.29];
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, HTML_MESSAGE=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: B2EC60EBDF826CA8C9BA23575B208470955DDF4B
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/UcTSCrO8y5YZni9xnZm_HAbsKhI>
Subject: [tcpm] Fwd: Delivery Status Notification (Failure)
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2018 13:33:05 -0000
JFYI … and, hm - I don’t think this makes things easier :( Maybe his mail box is just overloaded? Or maybe Google’s internal emails now get delivered with BBR ?? ;-D > Begin forwarded message: > > From: Mail Delivery Subsystem <mailer-daemon@googlemail.com> > Subject: Delivery Status Notification (Failure) > Date: March 13, 2018 at 1:11:30 PM GMT+1 > To: michawe@ifi.uio.no > Resent-From: <michawe@ifi.uio.no> > > > Message not delivered > There was a problem delivering your message to <>jri@google.com <mailto:jri@google.com>. See the technical details below. > Reporting-MTA: dns; googlemail.com <http://googlemail.com/> > Received-From-MTA: dns; michawe@ifi.uio.no <mailto:michawe@ifi.uio.no> > Arrival-Date: Tue, 13 Mar 2018 05:11:30 -0700 (PDT) > X-Original-Message-ID: <FF54A053-F7ED-4B94-B229-62C03339316F@ifi.uio.no <mailto:FF54A053-F7ED-4B94-B229-62C03339316F@ifi.uio.no>> > > Final-Recipient: rfc822; jri@google.com <mailto:jri@google.com> > Action: failed > Status: 5.0.0 > Last-Attempt-Date: Tue, 13 Mar 2018 05:11:30 -0700 (PDT) > > From: Michael Welzl <michawe@ifi.uio.no <mailto:michawe@ifi.uio.no>> > Subject: Re: [tcpm] [tsvwg] Agenda requests for TSVWG@IETF101 > Date: March 13, 2018 at 1:11:13 PM GMT+1 > To: "<gorry@erg.abdn.ac.uk <mailto:gorry@erg.abdn.ac.uk>> Fairhurst" <gorry@erg.abdn.ac.uk <mailto:gorry@erg.abdn.ac.uk>> > Cc: "Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com <mailto:michael.scharf@nokia.com>>, "tcpm-chairs@ietf.org <mailto:tcpm-chairs@ietf.org>" <tcpm@ietf.org <mailto:tcpm@ietf.org>>, "tsvwg-chairs@ietf.org <mailto:tsvwg-chairs@ietf.org>" <tsvwg-chairs@ietf.org <mailto:tsvwg-chairs@ietf.org>>, Jana Iyengar <jri@google.com <mailto:jri@google.com>> > > > Hi folks! > > I am puzzled as to why I receive this - has someone put me in bcc? AFAIK, I’m not in tcpm-chairs, not in tsvwg-chairs, and I’m also happy to remind people that I’m *not* chairing ICCRG anymore! :-) > > Anyway, to me, this also sounds like ICCRG material - but I haven’t read the draft and so I probably shouldn’t even comment. > But FWIW, I’d enjoy seeing this in ICCRG. I might even ask something at the mic, just to see how that feels. > > I’m cc’ing the ICCRG chair, Jana, because it seems that this should have reached him. > > Jana - I actually even can’t fully figure out what these folks here are talking about: either this draft: > https://datatracker.ietf.org/doc/draft-han-tsvwg-cc <https://datatracker.ietf.org/doc/draft-han-tsvwg-cc> <https://datatracker.ietf.org/doc/draft-han-tsvwg-cc <https://datatracker.ietf.org/doc/draft-han-tsvwg-cc>> > or that draft: > https://tools.ietf.org/html/draft-lochin-ietf-tsvwg-gtfrc-02 <https://tools.ietf.org/html/draft-lochin-ietf-tsvwg-gtfrc-02> <https://tools.ietf.org/html/draft-lochin-ietf-tsvwg-gtfrc-02 <https://tools.ietf.org/html/draft-lochin-ietf-tsvwg-gtfrc-02>> > > I think it’s the upper one. > > Cheers, > Michael > > >> On Mar 13, 2018, at 12:51 PM, Gorry Fairhurst <gorry@erg.abdn.ac.uk <mailto:gorry@erg.abdn.ac.uk>> wrote: >> >> On 13/03/2018, 11:23, Scharf, Michael (Nokia - DE/Stuttgart) wrote: >>>> As for TSVWG, we have had quite a long discussion with the authors at the >>>> meeting and after. The TSV chairs encouraged them to take the CC aspects >>>> separately and explain why this method is better and detail what this benefit >>>> is and what is required in the router to allow this. We suggested an initial talk >>>> in ICCRG to present results and show *why* this is attractive. As far as I know >>>> they requested time to do this. >>> ICCRG is the right home for this. And the TCPM charter explicitly allows us to move topics there... >>> >>> I have written a PhD thesis on exactly this topic; we had a network processor implementation of Quick-Start, and our use cases was actually augmented/virtual reality... And I run into tons of fundamental issues 10 years ago, which are not easy to solve and not even mentioned in the I-Ds. So I somehow feel qualified to give feedback on what they have to look at more in detail 😉 >>> >>>> They also requested time in TSVWG - but there's (as yet) been little discssion >>>> on the list, so we curently advise them to prepare a slide to show to say why >>>> people should read the draft. We have not decided (yet) to give time to this >>>> new framework. >>> I personally believe that for new ideas the IETF should give a presentation slot *once*. For a second presentation the bar should be higher. If the framework draft has been presented already in TSVWG, IMHO further discussion on that belongs now on the list. >>> >>>> They have now also requested time in TCPM. >>> The draft is very specific about TCP congestion control, so in principle it belongs into TCPM. In general, I think TCPM should be open to new ideas. But my own thinking is that this can be at best a "if time permits" presentation in TCPM. >>> >>>> I don't know whethere this time they are also requesting slots some other >>>> places to discuss other aspects. >>>> >>>> I also suggested (informally) that they should try making a great short >>>> presentation of how this is a new opportunity and whar has changed since >>>> we last saw schemes proposed. I do see that there are significant advances in >>>> router forwarding hardware - and I suspect there could be similar ideas in >>>> cisco, etc.Would other vendors (or operators) be interested in standardising >>>> this? I think such a talk could be put to TSVAREA. >>> I am only at the IETF on Sunday evening and Monday morning. Unfortunately, I may not be in TSVAREA as I have to go back to the airport. >>> >>> I doubt that other people who are familiar with RTG and OPS area will show up in TSVAREA (but I may be wrong). It is > ----- Message truncated -----
- [tcpm] Fwd: Delivery Status Notification (Failure) Michael Welzl