From nobody Mon Jun 1 10:23:31 2020 Return-Path: X-Original-To: babel@ietfa.amsl.com Delivered-To: babel@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E0E33A12ED for ; Mon, 1 Jun 2020 10:23:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.848 X-Spam-Level: X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 tyyPqWBUVdda for ; Mon, 1 Jun 2020 10:23:28 -0700 (PDT) Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8525B3A12EB for ; Mon, 1 Jun 2020 10:23:28 -0700 (PDT) Received: by mail-io1-xd34.google.com with SMTP id q8so7736855iow.7 for ; Mon, 01 Jun 2020 10:23:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=fth7IMH6Bq0FzWGJ5fh5jC0z6lBgZ3Jh+0N2bzLvteQ=; b=VN5XKIPo/5Lzg2GQxrxyMKbGXKqznUFXUq4ZMGlJxrNidGqi7cW8s6tYSESdcP+qjC euSNRz/nwFMCb0fCtebZibWyXezWgEUR+t39k0kDFpq8r3JS6JvxPq8i1+Bhk4nmHxGs lR0dRxli8QqvG8fc+6BMZ1F4wPee0pHqgnpCue1aTIFOI9NYIY1RPcj/tQib3mUtMvTk kDpQJJzBXVp2rJUQyNKE56S1qpl1i87HRsrQgmjYmsC24MmxL9xwJtGjdOJMJMNDqbjm paEiXrfcKRLgXXUqprrYnLw01t3ilWYsUDT/vdzYKVq3yplZosCYAmI4hxi15yyzsFYZ 2+mg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=fth7IMH6Bq0FzWGJ5fh5jC0z6lBgZ3Jh+0N2bzLvteQ=; b=pctxd/1QRPUuvhVhgk4S1Nu1M/ovPCZl0dWnFQuQXDIDHfASw3BKyoHCrukUJzw339 yBYqoCnJvgEfe9m6S2j7DBrL4RiS4oASwPGJeyD4KPtRuH0dH7+DAR7PcsmS+bgvZsFv OMzbO2KAwSuqxcyA+ESCeHHIU+jlgn7E1OvANsDhGmpX4DadUB4//hNT8CmyRXM7LC0R nsPbt7UUhxZgloTpryJg+t/Pk993F9gjSjkljjS9/9VXHe+dhN9i4quWOc0YaVX8zGIv fwUKQZWszBbgu77rizUZenxvduAqmniwa4yK9Rd558vxYeSPcVDnt1IYOztqVJX3Xdxq VlMA== X-Gm-Message-State: AOAM530qGFK5AUswVoVUuiZunEuAhHuXNLPgkuLCpxT/hdPMdy70PTus qIGXev+Feccws74TmXVbL7GDlMl4ORKxAnUPX97Lzaun X-Google-Smtp-Source: ABdhPJzlSZ3g/QNYjUkAV3/F3JCurTBn4h8CmfN1WCUbGxhfKwR9UvYWNJsVXtkcmq0v/FIhZaj+41Y3cc8o64Gj9GA= X-Received: by 2002:a02:14c8:: with SMTP id 191mr8597936jag.39.1591032207344; Mon, 01 Jun 2020 10:23:27 -0700 (PDT) MIME-Version: 1.0 References: <159060174027.19786.17250259010206020465@ietfa.amsl.com> In-Reply-To: <159060174027.19786.17250259010206020465@ietfa.amsl.com> From: Donald Eastlake Date: Mon, 1 Jun 2020 13:23:16 -0400 Message-ID: To: Babel at IETF Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: [babel] Fwd: Nomcom 2020-2021 Call For Volunteers X-BeenThere: babel@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A list for discussion of the Babel Routing Protocol." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jun 2020 17:23:30 -0000 ---------- Forwarded message --------- From: NomCom Chair 2020 Date: Wed, May 27, 2020 at 4:37 PM Subject: Nomcom 2020-2021 Call For Volunteers To: IETF Announcement List Cc: The IETF NomCom appoints people to fill the open slots on the LLC, IETF Trust, the IAB, and the IESG. Ten voting members for the NomCom are selected in a verifiably random way from a pool of volunteers. The more volunteers, the better chance we have of choosing a random yet representative cross section of the IETF population. The details of the operation of the NomCom can be found in BCP 10 (RFC 8713). RFC 3797 details the selection algorithm. Special for this year (and only this year), we also have RFC 8788 (one-off update to RFC 8713 / BCP 10) to tell us who is eligible to volunteer: Members of the IETF community must have attended at least three of the last five in-person IETF meetings in order to volunteer. The five meetings are the five most recent in-person meetings that ended prior to the date on which the solicitation for NomCom volunteers was submitted for distribution to the IETF community. Because no IETF 107 in-person meeting was held, for the 2020-2021 Nominating Committee those five meetings are IETFs 102 [Montreal, Canada; July 2018], 103 [Bangkok, Thailand; November 2018], 104 [Prague, Czech Republic; March 2019], 105 [Montreal, Canada; July 2019], and 106 [Singapore; November 2019]. Keep in mind that eligibility is based on in-person attendance at the five listed meetings. You can check your eligibility at: https://www.ietf.org/registration/nomcom.py. If you qualify, please volunteer. Before you decide to volunteer, please remember that anyone appointed to this NomCom will not be considered as a candidate for any of the positions that the 2020 - 2021 NomCom is responsible for filling. People commonly volunteer by ticking the box on IETF registration forms. The IETF 106 form did not ask whether people were willing to volunteer. IETF 107 did ask, but all those registrations were canceled. I have asked the Secretariat if it is possible to get the list if volunteers from canceled IETF 107 registrations. If that list is available, I will contact all who are verified as eligible. But given the uncertainty of this process, I would encourage people to volunteer directly (see the bottom of this email for instructions). Thank you for volunteering! The list of people and posts whose terms end with the March 2021 IETF meeting, and thus the positions for which this NomCom is responsible, are IETF Trust: Joel Halpern LLC: Maja Andjelkovic IAB: Jari Arkko Jeff Tantsura Mark Nottingham Stephen Farrell Wes Hardaker Zhenbin Li IESG: Alissa Cooper, IETF Chair/GEN AD Alvaro Retana, RTG AD Barry Leiba, ART AD Deborah Brungard, RTG AD =C3=89ric Vyncke, INT AD Magnus Westerlund, TSV AD Roman Danyliw, SEC AD Warren Kumari, OPS AD All appointments are for 2 years. The Routing area has 3 ADs and the General area has 1; all other areas have 2 ADs. Thus, all areas (that have more than one AD) have at least one continuing AD. The primary activity for this NomCom will begin in July 2020 and should be completed in January 2021. The NomCom will have regularly scheduled conference calls to ensure progress. There will be activities to collect requirements from the community, review candidate questionnaires, review feedback from community members about candidates, and talk to candidates. While being a NomCom member does require some time commitment it is also a very rewarding experience. As a member of the NomCom it is very important that you be willing and able to attend either videoconference or in-person meetings (which may not happen) during 14-20 November (IETF 109 - Bangkok) to conduct interviews. Videoconference attendance will be supported whether or not there are in-person meetings. Orientation and setting of the NomCom schedule will be done by videoconference during the week 20-24 July (exact time and date to be determined after NomCom membership is finalized on July 12), the week prior to IETF 108. Being at IETF 110 (Prague) is not essential. Please volunteer by sending me an email before 23:59 UTC June 24, 2020, as follows: To: nomcom-chair-2020@ietf.org Subject: NomCom 2020-21 Volunteer Please include the following information in the email body: Your Full Name: __________ // as you write it on the IETF registration form Current Primary Affiliation: // Typically what goes in the Company field // in the IETF Registration Form Emails: _______________ // All email addresses used to register for the past 5 IETF meetings // Preferred email address first Telephone: _______________________ // For confirmation if selected You should expect an email response from me within 5 business days stating whether or not you are qualified. If you don't receive this response, please re-send your email with the tag "RESEND"" added to the subject line. If you are not yet sure if you would like to volunteer, please consider that NomCom members play a very important role in shaping the leadership of the IETF. Questions by email or voice are welcome. Volunteering for the NomCom is a great way to contribute to the IETF! You can find a detailed timeline on the NomCom web site at: https://datatracker.ietf.org/nomcom/2019/ I will be publishing a more detailed target timetable, as well as details of the randomness seeds to be used for the RFC 3797 selection process, within the next few weeks. Thank you! Barbara Stark bs7652 at att dot com nomcom-chair-2020 at ietf dot org _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce From nobody Wed Jun 17 06:32:43 2020 Return-Path: X-Original-To: babel@ietfa.amsl.com Delivered-To: babel@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 151873A0796 for ; Wed, 17 Jun 2020 06:32:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 RxDJbsXzwIBc for ; Wed, 17 Jun 2020 06:32:40 -0700 (PDT) Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F3403A0795 for ; Wed, 17 Jun 2020 06:32:40 -0700 (PDT) Received: by mail-wr1-x436.google.com with SMTP id h5so2365408wrc.7 for ; Wed, 17 Jun 2020 06:32:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:subject:from:to:date:message-id :in-reply-to; bh=Ecr307euS+QZVUWDEh74GvyQlwb+ltipjCuLxsVV2+Q=; b=UzXVDdwSbFpx4xFVv6bP5sm7Ujx9bfOptJxp35oAZIn0nsS2nRtGyWYNgNOgY5QCy1 RFKU53+G9PxkaVr7AlVl1N5ODpzMo3hmKVSIYsKXbvYO7l5TzMhePtR0SWINaJMe9y0V wa5URLVV5L4o5ZKUJ7SuBpzYAm5ldvG7/Kvg3nTVUXWnYzH+0MUrPM6DsyMDWusXbaaL 7sqOzfX1mPvm7bJBSXkLoJsb9W8URmhTiCjNMlsKfe+NkqNi8bqifZIa4pZegS2O71bO naEyGxB9PpIdWXun42F/cpg0RrpxC3jPwT8v9NQtCltW3ZHFt5+eO9vhCxaVGVhG1DeG nvSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:subject:from:to:date :message-id:in-reply-to; bh=Ecr307euS+QZVUWDEh74GvyQlwb+ltipjCuLxsVV2+Q=; b=oNvaiaNJfyFxVD39/EKNs2ken+OsXfGn/o4k418xTT/Hp6/tIIuqvwI1kcD4dotG8H SYfCcIf4kghglwdQOx3sfBmx2mxzStZ00vAxyV/3ukLT6gbewSrJQNNByFZrYySXialP 99qTkSUs5TDx1aVnIE9n3tQ4I18bm275h1BE1CyT8VYnG0UHFt4qH8nfOBM1xWGdbsVM zNsH4DvE2j4TaK8yPUBS7n/1UeF13aP7Tb7Rl7iybbudwRdAmnfLbTa5X1ZAFvhoWseU 37BxSqwHp6xmevVcxzokQx7J5ohIni+FkigUzWrFJKEFaKx6a8Iw6uXDVKy/JuH4fHM2 7t6A== X-Gm-Message-State: AOAM531Agh0Le3ET5oQ0mpc2NYY/VVOHjf54bly2ZyyJVnfTvgf0Lr40 DGiQ06GkGEkLttW1dkTj1/U= X-Google-Smtp-Source: ABdhPJyzLq8VKztEg+CL6nuqHuZtSl/vDzNjwkrrOUzX2LmW4TcqdiGlt9KlG82qfqI2NNT/iF2hKQ== X-Received: by 2002:a5d:6305:: with SMTP id i5mr8374753wru.268.1592400758866; Wed, 17 Jun 2020 06:32:38 -0700 (PDT) Received: from localhost (2a01cb0802a2e700020ec6fffed9ad5a.ipv6.abo.wanadoo.fr. [2a01:cb08:2a2:e700:20e:c6ff:fed9:ad5a]) by smtp.gmail.com with ESMTPSA id t8sm388571wmi.46.2020.06.17.06.32.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 17 Jun 2020 06:32:38 -0700 (PDT) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 From: =?utf-8?q?Antonin_D=C3=A9cimo?= To: "Barbara H. Stark" , "Mahesh Jethanandani" , "babel@ietf.org" Date: Wed, 17 Jun 2020 15:18:07 +0200 Message-Id: In-Reply-To: Archived-At: Subject: Re: [babel] [patch] Info model: fix little inconsistencies in naming, use singular for objects. X-BeenThere: babel@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A list for discussion of the Babel Routing Protocol." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2020 13:32:42 -0000 Hello Barbara, hello Mahesh, hello list! I hope everyone is doing well. I had some time on my hands and decided to write clean patches for the issues I raised concerning the Information Model draft. I opened a pull request on GitHub here. https://github.com/bhstark2/babel-information-model/pull/22 I hope there=E2=80=99s a way to see them incorporated in the draft. Antonin D=C3=A9cimo (4): bump year to 2020 don't pluralize *-obj fix naming inconsistencies uniformize and don't indent artwork draft-ietf-babel-information-model.md | 226 +++++++++++++------------- 1 file changed, 113 insertions(+), 113 deletions(-) Best regards, -- Antonin From nobody Thu Jun 18 19:54:43 2020 Return-Path: X-Original-To: babel@ietfa.amsl.com Delivered-To: babel@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6079E3A0B0C for ; Thu, 18 Jun 2020 19:54:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.847 X-Spam-Level: X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 faEZqZzUWCc6 for ; Thu, 18 Jun 2020 19:54:36 -0700 (PDT) Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5972A3A107D for ; Thu, 18 Jun 2020 19:54:36 -0700 (PDT) Received: by mail-io1-xd2e.google.com with SMTP id t9so9595082ioj.13 for ; Thu, 18 Jun 2020 19:54:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=pInZ+bEBdaaFyFAEr+HjAXyGTQnvdXJBM3IMgaxPZOk=; b=l9ax/cSm1SRP+QH2UiFC0IJCA1oaQ4bnYO2nIRuKHr00lzbhHfG6HZl09O3bjE+ccC M+wmJe8iS4+C0zab3iPUcCsI1WaKr++t0QS/XujUZr4x3wt5tYoWDcSkANg1Xv3Xp3D0 BHrhFC30Xln2TRzqBa50fmM7e1klFuIUFV1fjLxY5TD3C0uJfQf9h5keZ/WDAeuBEJPR Xq8gwQaFs+7E/l8z/D3AOZV4Z2VYLd7brKt6gzpjfCAll4N/OvSpbwRcrtWHmJIfiNjj YipnjfsLDBcpjkmFOVG59eJOEMoU++dErEiIr+ykESwL7mymQamJ5ejyJfbgC/NpTxeo wHIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=pInZ+bEBdaaFyFAEr+HjAXyGTQnvdXJBM3IMgaxPZOk=; b=Inn3/5tp7OUdxa8q7wBYaTaKT+JH3wIgjh0SI9dTr3IMl0O0HpfHJm45tTv6L2ltvU Mzu6mOIH3WaVrXqtA2RJ+BxqT0mXnWnZw1qts1FSPw8QPP7pPK3p/brmm+SVODrbUHf1 QBtTyVkwiyfEA3gHd/eBBeU/xsBe4+q2sHprOcviAKAdrzCAkaySAPlKe2kjmgSaKaNS u9rUfqs3RR4Yx83nTlFQ/NVIdltLUsnsqQ7y7JP9Ka0/QBBMJuWz1QmyVn3vIsbt5KP5 qPmtEamJhPfaVN4hVzTV0/5f9hKc3fY2Iku8mhn6pfYAQmSmHd0q/RayDViCC0f/Zsnd 8fEw== X-Gm-Message-State: AOAM532AFEKYoBJFP8JWakmTyD3bT2yD5bppPF3T65M2Tt3mJlnIAdRQ KbYpZ5l6W/vevN3yBxcH/jhdcbYmeu3G8K640yCxHWo4 X-Google-Smtp-Source: ABdhPJwQT7iiOuftB1CRUe0anxZDu4UWD/wcVG/F5TZmZ8RtXocbfNy8JHLI+PPpCFU7xxANCxS2dg7f/X7Azyl2d4g= X-Received: by 2002:a6b:2c1:: with SMTP id 184mr1965490ioc.167.1592535275153; Thu, 18 Jun 2020 19:54:35 -0700 (PDT) MIME-Version: 1.0 References: <159181529656.16063.6964178024900109434@ietfa.amsl.com> In-Reply-To: <159181529656.16063.6964178024900109434@ietfa.amsl.com> From: Donald Eastlake Date: Thu, 18 Jun 2020 22:54:23 -0400 Message-ID: To: Babel at IETF Content-Type: multipart/alternative; boundary="0000000000005e35dc05a867031f" Archived-At: Subject: [babel] Fwd: Nomcom 2020-2021 Second Call For Volunteers X-BeenThere: babel@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A list for discussion of the Babel Routing Protocol." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jun 2020 02:54:38 -0000 --0000000000005e35dc05a867031f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ---------- Forwarded message --------- From: NomCom Chair 2020 Date: Wed, Jun 10, 2020 at 2:55 PM Subject: Nomcom 2020-2021 Second Call For Volunteers To: IETF Announcement List Cc: This is the second sending of the call for volunteers for the 2020-2021 NomCom. I wanted to mention a few updates from the previous email (sent 2 weeks ago): - I've fixed the URL at the bottom of the email to point to https://datatracker.ietf.org/nomcom/2020/ instead of /2019/. This was a test to see if anyone was paying attention. Apparently, some people were. ;= ) - The IETF 108 registration form includes a checkbox that will let you volunteer. You can use this instead of emailing me, when you register for IETF 108. - I currently have 39 volunteers. Last year had 149. I need more volunteers! ---------------------------------------------------------------------------= ------ The IETF NomCom appoints people to fill the open slots on the LLC, IETF Trust, the IAB, and the IESG. Ten voting members for the NomCom are selected in a verifiably random way from a pool of volunteers. The more volunteers, the better chance we have of choosing a random yet representative cross section of the IETF population. The details of the operation of the NomCom can be found in BCP 10 (RFC 8713). RFC 3797 details the selection algorithm. Special for this year (and only this year), we also have RFC 8788 (one-off update to RFC 8713 / BCP 10) to tell us who is eligible to volunteer: Members of the IETF community must have attended at least three of the last five in-person IETF meetings in order to volunteer. The five meetings are the five most recent in-person meetings that ended prior to the date on which the solicitation for NomCom volunteers was submitted for distribution to the IETF community. Because no IETF 107 in-person meeting was held, for the 2020-2021 Nominating Committee those five meetings are IETFs 102 [Montreal, Canada; July 2018], 103 [Bangkok, Thailand; November 2018], 104 [Prague, Czech Republic; March 2019], 105 [Montreal, Canada; July 2019], and 106 [Singapore; November 2019]. Keep in mind that eligibility is based on in-person attendance at the five listed meetings. You can check your eligibility at: https://www.ietf.org/registration/nomcom.py. If you qualify, please volunteer. Before you decide to volunteer, please remember that anyone appointed to this NomCom will not be considered as a candidate for any of the positions that the 2020 - 2021 NomCom is responsible for filling. People commonly volunteer by ticking the box on IETF registration forms. The IETF 106 form did not ask whether people were willing to volunteer. IETF 107 did ask, but all those registrations were canceled. I have asked the Secretariat if it is possible to get the list if volunteers from canceled IETF 107 registrations. If that list is available, I will contact all who are verified as eligible. But given the uncertainty of this process, I would encourage people to volunteer directly (see the bottom of this email for instructions). Thank you for volunteering! The list of people and posts whose terms end with the March 2021 IETF meeting, and thus the positions for which this NomCom is responsible, are IETF Trust: Joel Halpern LLC: Maja Andjelkovic IAB: Jari Arkko Jeff Tantsura Mark Nottingham Stephen Farrell Wes Hardaker Zhenbin Li IESG: Alissa Cooper, IETF Chair/GEN AD Alvaro Retana, RTG AD Barry Leiba, ART AD Deborah Brungard, RTG AD =C3=89ric Vyncke, INT AD Magnus Westerlund, TSV AD Roman Danyliw, SEC AD Warren Kumari, OPS AD All appointments are for 2 years. The Routing area has 3 ADs and the General area has 1; all other areas have 2 ADs. Thus, all areas (that have more than one AD) have at least one continuing AD. The primary activity for this NomCom will begin in July 2020 and should be completed in January 2021. The NomCom will have regularly scheduled conference calls to ensure progress. There will be activities to collect requirements from the community, review candidate questionnaires, review feedback from community members about candidates, and talk to candidates. While being a NomCom member does require some time commitment it is also a very rewarding experience. As a member of the NomCom it is very important that you be willing and able to attend either videoconference or in-person meetings (which may not happen) during 14-20 November (IETF 109 - Bangkok) to conduct interviews. Videoconference attendance will be supported whether or not there are in-person meetings. Orientation and setting of the NomCom schedule will be done by videoconference during the week 20-24 July (exact time and date to be determined after NomCom membership is finalized on July 12), the week prior to IETF 108. Being at IETF 110 (Prague) is not essential. Please volunteer by sending me an email before 23:59 UTC June 24, 2020, as follows: To: nomcom-chair-2020@ietf.org Subject: NomCom 2020-21 Volunteer Please include the following information in the email body: Your Full Name: // as you write it on the IETF registration form Current Primary Affiliation: // Typically what goes in the Company field // in the IETF Registration Form Emails: // All email addresses used to register for the past 5 IETF meetings // Preferred email address first Telephone: // For confirmation if selected You should expect an email response from me within 5 business days stating whether or not you are qualified. If you don't receive this response, please re-send your email with the tag "RESEND"" added to the subject line. If you are not yet sure if you would like to volunteer, please consider that NomCom members play a very important role in shaping the leadership of the IETF. Questions by email or voice are welcome. Volunteering for the NomCom is a great way to contribute to the IETF! You can find a detailed timeline on the NomCom web site at: https://datatracker.ietf.org/nomcom/2020/ I will be publishing a more detailed target timetable, as well as details of the randomness seeds to be used for the RFC 3797 selection process, within the next few weeks. Thank you! Barbara Stark bs7652 at att dot com nomcom-chair-2020 at ietf dot org --0000000000005e35dc05a867031f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
---------- Forwarded message ---------
From: NomCom Chair 2020 &= lt;nomcom-chair-2020@ietf.org= >
Date: Wed, Jun 10, 2020 at 2:55 PM
Subject: Nomcom 20= 20-2021 Second Call For Volunteers
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: = <ietf@ietf.org>

This is the second sending of the call for volunteers for the 2020-2021 No= mCom.

I wanted to mention a few updates from the previous email (sent 2 weeks ago= ):
=C2=A0- I've fixed the URL at the bottom of the email to point to https://datatracker.ietf.org/nomcom/2020/ instead of /2019/= . This was a test to see if anyone was paying attention. Apparently, some p= eople were. ;)
=C2=A0- The IETF 108 registration form includes a checkbox that will let yo= u volunteer. You can use this instead of emailing me, when you register for= IETF 108.
=C2=A0- I currently have 39 volunteers. Last year had 149. I need more volu= nteers!
---------------------------------------------------------------------------= ------
The IETF NomCom appoints people to fill the open slots on the LLC, IETF Tru= st, the IAB, and the IESG.

Ten voting members for the NomCom are selected in a verifiably random way f= rom a pool of volunteers. The more volunteers, the better chance we have of= choosing a random yet representative cross section of the IETF population.=

The details of the operation of the NomCom can be found in BCP 10 (RFC 8713= ). RFC 3797 details the selection algorithm.

Special for this year (and only this year), we also have RFC 8788 (one-off = update to RFC 8713 / BCP 10) to tell us who is eligible to volunteer:

=C2=A0 =C2=A0 =C2=A0 Members of the IETF community must have attended at le= ast three of
=C2=A0 =C2=A0 =C2=A0 the last five in-person IETF meetings in order to volu= nteer.

=C2=A0 =C2=A0 =C2=A0 The five meetings are the five most recent in-person m= eetings that
=C2=A0 =C2=A0 =C2=A0 ended prior to the date on which the solicitation for = NomCom
=C2=A0 =C2=A0 =C2=A0 volunteers was submitted for distribution to the IETF = community.
=C2=A0 =C2=A0 =C2=A0 Because no IETF 107 in-person meeting was held, for th= e 2020-2021
=C2=A0 =C2=A0 =C2=A0 Nominating Committee those five meetings are IETFs
=C2=A0 =C2=A0 =C2=A0 =C2=A0 102 [Montreal, Canada; July 2018],
=C2=A0 =C2=A0 =C2=A0 =C2=A0 103 [Bangkok, Thailand; November 2018],
=C2=A0 =C2=A0 =C2=A0 =C2=A0 104 [Prague, Czech Republic; March 2019],
=C2=A0 =C2=A0 =C2=A0 =C2=A0 105 [Montreal, Canada; July 2019], and
=C2=A0 =C2=A0 =C2=A0 =C2=A0 106 [Singapore; November 2019].

Keep in mind that eligibility is based on in-person attendance at the five = listed meetings. You can check your eligibility at: https= ://www.ietf.org/registration/nomcom.py.

If you qualify, please volunteer. Before you decide to volunteer, please re= member that anyone appointed to this NomCom will not be considered as a can= didate for any of the positions that the 2020 - 2021 NomCom is responsible = for filling.

People commonly volunteer by ticking the box on IETF registration forms. Th= e IETF 106 form did not ask whether people were willing to volunteer. IETF = 107 did ask, but all those registrations were canceled. I have asked the Se= cretariat if it is possible to get the list if volunteers from canceled IET= F 107 registrations. If that list is available, I will contact all who are = verified as eligible. But given the uncertainty of this process, I would en= courage people to volunteer directly (see the bottom of this email for inst= ructions). Thank you for volunteering!

The list of people and posts whose terms end with the March 2021 IETF meeti= ng, and thus the positions for which this NomCom is responsible, are

IETF Trust:
=C2=A0 =C2=A0 Joel Halpern

LLC:
=C2=A0 =C2=A0 Maja Andjelkovic

IAB:
=C2=A0 =C2=A0 Jari Arkko
=C2=A0 =C2=A0 Jeff Tantsura
=C2=A0 =C2=A0 Mark Nottingham
=C2=A0 =C2=A0 Stephen Farrell
=C2=A0 =C2=A0 Wes Hardaker
=C2=A0 =C2=A0 Zhenbin Li

IESG:
=C2=A0 =C2=A0 Alissa Cooper, IETF Chair/GEN AD
=C2=A0 =C2=A0 Alvaro Retana, RTG AD
=C2=A0 =C2=A0 Barry Leiba, ART AD
=C2=A0 =C2=A0 Deborah Brungard, RTG AD
=C2=A0 =C2=A0 =C3=89ric Vyncke, INT AD
=C2=A0 =C2=A0 Magnus Westerlund, TSV AD
=C2=A0 =C2=A0 Roman Danyliw, SEC AD
=C2=A0 =C2=A0 Warren Kumari, OPS AD

All appointments are for 2 years. The Routing area has 3 ADs and the Genera= l area has 1; all other areas have 2 ADs. Thus, all areas (that have more t= han one AD) have at least one continuing AD.

The primary activity for this NomCom will begin in July 2020 and should be = completed in January 2021.=C2=A0 The NomCom will have regularly scheduled c= onference calls to ensure progress. There will be activities to collect req= uirements from the community, review candidate questionnaires, review feedb= ack from community members about candidates, and talk to candidates.

While being a NomCom member does require some time commitment it is also a = very rewarding experience.

As a member of the NomCom it is very important that you be willing and able= to attend either videoconference or in-person meetings (which may not happ= en) during 14-20 November (IETF 109 - Bangkok) to conduct interviews. Video= conference attendance will be supported whether or not there are in-person = meetings. Orientation and setting of the NomCom schedule will be done by vi= deoconference during the week 20-24 July (exact time and date to be determi= ned after NomCom membership is finalized on July 12), the week prior to IET= F 108.=C2=A0 Being at IETF 110 (Prague) is not essential.

Please volunteer by sending me an email before 23:59 UTC June 24, 2020, as = follows:

To: nomcom-= chair-2020@ietf.org
Subject: NomCom 2020-21 Volunteer

Please include the following information in the email body:

Your Full Name:
=C2=A0 =C2=A0 // as you write it on the IETF registration form

Current Primary Affiliation:
=C2=A0 =C2=A0 // Typically what goes in the Company field
=C2=A0 =C2=A0 // in the IETF Registration Form

Emails:
=C2=A0 =C2=A0// All email addresses used to register for the past 5 IETF me= etings
=C2=A0 =C2=A0// Preferred email address first

Telephone:
=C2=A0 =C2=A0 // For confirmation if selected

You should expect an email response from me within 5 business days stating = whether or not you are qualified.=C2=A0 If you don't receive this respo= nse, please re-send your email with the tag "RESEND"" added = to the subject line.

If you are not yet sure if you would like to volunteer, please consider tha= t NomCom members play a very important role in shaping the leadership of th= e IETF.=C2=A0 Questions by email or voice are welcome. Volunteering for the= NomCom is a great way to contribute to the IETF!

You can find a detailed timeline on the NomCom web site at:
=C2=A0 =C2=A0 https://datatracker.ietf.org/nomcom/2020/=

I will be publishing a more detailed target timetable, as well as details o= f the randomness seeds to be used for the RFC 3797 selection process, withi= n the next few weeks.

Thank you!

Barbara Stark
bs7652 at att dot com
nomcom-chair-2020 at ietf dot org

--0000000000005e35dc05a867031f-- From nobody Fri Jun 26 08:14:30 2020 Return-Path: X-Original-To: babel@ietfa.amsl.com Delivered-To: babel@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D443A3A07C3 for ; Fri, 26 Jun 2020 08:14:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.848 X-Spam-Level: X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 tXKT3YAS54GA for ; Fri, 26 Jun 2020 08:14:27 -0700 (PDT) Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56ACF3A07C6 for ; Fri, 26 Jun 2020 08:14:27 -0700 (PDT) Received: by mail-io1-xd30.google.com with SMTP id q8so10196861iow.7 for ; Fri, 26 Jun 2020 08:14:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=pMJYdSMzM9PqP06r18FUJoHuns+tH5JvRbZ+8sq9F8E=; b=Cl+J6dVcNCTgLf/dDTd9fuySmVyqzHVosr2LZJe6rx5eEHDEdAJXm6bHPho6ATmDrF O6GL8mMjkA1Nc0UHhfJ0uchGwoPCG2SAr0sfXf2lLpqkqrybWPkMe3n4R6O60zjMpAMs iX3GKZzOCUhvv4r3mG+K/FFgzzzmjKaHDjU8VI4JukEytCcMw92z+UBxj1o0zlvKgddv gMV+D7wyBpRazGTw1vj3HUwOo1d1YkoYkMqE/JLj22Jqv5QInKZ6uKAMfrTVqywwlCbj nZ4FuWnadm+LvZ/ew9nNlYn26I4GqBxXF33v4TCs4DAU54rRijTwPOY3tfOu2Z+3karY eHbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=pMJYdSMzM9PqP06r18FUJoHuns+tH5JvRbZ+8sq9F8E=; b=n0CrcuFM/NzuZz9FBUDgTOl6sBjV/WKq3gX19QRJAXN6lzbwg0VD0dCWyETm1pdTn+ ycr2BBSQND1oUofEnGFlGRQ0wJV1x3dD2ELilhVM2PfOf4zrRMhNJFeZNYK5GcLODXxW AvLRYYkYfm5K+la22dmdiDF910eHZcmFL7cZaZ+nMNxkbBMvw9+h8QbewzvWbbnxoAkh rJq0CPYlgAzPpd+SEnfmuILWNlCGvzP99E5x8Zx0MFSi0nog72F9GqkyCBCsplOifUKw RPo3XRcNsUxGR+33049UD+BxY4874xKIiwwMKB43lk/gWuC4TPR5Tq+5jMcPHM8EXxIT dHXQ== X-Gm-Message-State: AOAM533dyUqjEolJQn1UFbfS5qCL9DgB9LpZ99JYI4c9PxMCEJoEBH1o TG0TBFheqp4mX6A/+tZiFaR/4p8RTAnEmmCNl4SwPExuNKI= X-Google-Smtp-Source: ABdhPJyayKYfo4Am18d7HaIuFR0p5TE3Gvl79TIFBbi53SLZAyp474HR7i9VEZCkbWHgDYnEJkSEGh1NPZcjM2CYquM= X-Received: by 2002:a6b:2c1:: with SMTP id 184mr3865130ioc.167.1593184466087; Fri, 26 Jun 2020 08:14:26 -0700 (PDT) MIME-Version: 1.0 References: <159318112849.29459.4852442286238599577@ietfa.amsl.com> In-Reply-To: <159318112849.29459.4852442286238599577@ietfa.amsl.com> From: Donald Eastlake Date: Fri, 26 Jun 2020 11:14:14 -0400 Message-ID: To: Babel at IETF Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: [babel] Fwd: IETF 108 Online: Early Bird Registration Ends Today! X-BeenThere: babel@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A list for discussion of the Babel Routing Protocol." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2020 15:14:29 -0000 Hi, Sorry to forward this a bit late. The upcoming IETF meeting will be virtual (see https://www.ietf.org/how/meetings/108/). Normally remote participation in IETF meetings is free and the fees paid by those attending provide substantial income to help cover the IETF's costs. Thus, this time, there are fees for remote participation (although I believe listening to the audio streaming will still be free). There is a discount for one day participation and for students. If you plan to participate and can afford to do so, you should register and pay. If you cannot afford to do so, there is a waiver mechanism so you can register without paying. Thanks, Donald =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D Donald E. Eastlake 3rd +1-508-333-2270 (cell) 2386 Panoramic Circle, Apopka, FL 32703 USA d3e3e3@gmail.com ---------- Forwarded message --------- From: IETF Secretariat Date: Fri, Jun 26, 2020 at 10:19 AM Subject: IETF 108 Online: Early Bird Registration Ends Today! To: IETF Announcement List Cc: <108all@ietf.org>, IETF 108 Online July 27-31, 2020 Hosted By: Ericsson IETF 108 Information: https://www.ietf.org/how/meetings/108/ Register online at: https://ietf.org/how/meetings/register/ 1. Registration 2. Fee Waivers 3. Hackathon 1. Registration: Early Bird Deadline The early bird deadline for registration is today, Friday, June 26t= h. Be sure to register and pay before the deadline passes! Register online at: https://registration.ietf.org/108/ NOTE: Payment is required at the time of registration. The Early Bi= rd registration fee is $230 USD until Friday, June 26th at UTC 23:59. After June 26th at UTC 23:59 the registration fee will be $280 USD = until the next registration deadline on July 20th, at which time the registration fee will become $330 USD. 2. Fee Waivers: The IETF provides fee waivers for the IETF 108 meeting to support t= hose for whom the registration fee represents a barrier to participation= . Please respect this and only request a fee waiver if that applies t= o you. If you need to request a fee waiver, you can do so at https://www.ietf.org/how/meetings/108/108-registration-fee-waiver/. 3. Hackathon: The IETF is holding a Hackathon to encourage developers to discuss, collaborate and develop utilities, ideas, sample code and solutions that show practical implementations of IETF standards. When: Monday, July 20 through July 24, 2020 Signup for the Hackathon: https://registration.ietf.org/108/new/hackathon/ More information can be found here: https://www.ietf.org/how/runningcode/hackathons/108-hackathon/ Keep up to date by subscribing to: https://www.ietf.org/mailman/listinfo/hackathon The Hackathon is free to attend and open to all. Extend the invitation to colleagues outside the IETF! Descriptions and information regarding the technologies for the hackathon are located on the IETF 108 Meeting Wiki: https://trac.ietf.org/trac/ietf/meeting/wiki/108hackathon Don=E2=80=99t see anything that interests you? Feel free to add your preferred technology to the list, sign up as its Champion and show up to work on it. Note: you must login to the wiki to add content. If you do add a new technology, we strongly suggest that you send an email to hackathon@ietf.org to let others know. You may generate interest in your technology, and find other people who want to contribute to it. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce From nobody Fri Jun 26 10:57:50 2020 Return-Path: X-Original-To: babel@ietfa.amsl.com Delivered-To: babel@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25F863A0BD4 for ; Fri, 26 Jun 2020 10:57:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 ICDlQDKYloDa for ; Fri, 26 Jun 2020 10:57:47 -0700 (PDT) Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 37FF23A0BD3 for ; Fri, 26 Jun 2020 10:57:46 -0700 (PDT) Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 05QHvhBE009432 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 26 Jun 2020 19:57:43 +0200 Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/82085) with ESMTP id 05QHvhx6031727; Fri, 26 Jun 2020 19:57:43 +0200 Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 0886FFA13F; Fri, 26 Jun 2020 19:57:43 +0200 (CEST) X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id sNmfCwT2DU_N; Fri, 26 Jun 2020 19:57:41 +0200 (CEST) Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 0E335FA13D; Fri, 26 Jun 2020 19:57:39 +0200 (CEST) Date: Fri, 26 Jun 2020 19:57:38 +0200 Message-ID: <87d05lwvzh.wl-jch@irif.fr> From: Juliusz Chroboczek To: Donald Eastlake Cc: Babel at IETF In-Reply-To: References: <159318112849.29459.4852442286238599577@ietfa.amsl.com> User-Agent: Wanderlust/2.15.9 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Fri, 26 Jun 2020 19:57:43 +0200 (CEST) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 26 Jun 2020 19:57:43 +0200 (CEST) X-Miltered: at korolev with ID 5EF63717.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-Miltered: at potemkin with ID 5EF63717.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 5EF63717.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/ X-j-chkmail-Enveloppe: 5EF63717.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/ X-j-chkmail-Score: MSGID : 5EF63717.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000 X-j-chkmail-Score: MSGID : 5EF63717.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000 X-j-chkmail-Status: Ham X-j-chkmail-Status: Ham Archived-At: Subject: Re: [babel] Fwd: IETF 108 Online: Early Bird Registration Ends Today! X-BeenThere: babel@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A list for discussion of the Babel Routing Protocol." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2020 17:57:49 -0000 > Thus, this time, there are fees for remote participation (although I > believe listening to the audio streaming will still be free). Could you please confirm the latter point? If that's not the case, I'd rather we didn't have a meeting. Thanks, -- Juliusz From nobody Fri Jun 26 11:23:43 2020 Return-Path: X-Original-To: babel@ietfa.amsl.com Delivered-To: babel@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60B673A0BEB for ; Fri, 26 Jun 2020 11:23:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.848 X-Spam-Level: X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 dfy4rzCOhgcT for ; Fri, 26 Jun 2020 11:23:41 -0700 (PDT) Received: from mail-il1-x131.google.com (mail-il1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58C2B3A0BE6 for ; Fri, 26 Jun 2020 11:23:41 -0700 (PDT) Received: by mail-il1-x131.google.com with SMTP id c75so9280311ila.8 for ; Fri, 26 Jun 2020 11:23:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rO0VyFuqIyykIKWwFkFb/s9ob+da8oVyY9E4V4Pm87w=; b=KSAXnHe6afB5suIUFGF2bmKsP4QlYKxd2nKQt19dvbOwSneq1vAjF3W9ufMW8ih58h dra4VSOIfH2aJnI+yZ9Vcy0BaHmtsovHq+vPbFfcEE4RsV9mDkLCfxtZioaIROxYYyff 4S14UewOgCc3bGPYckhuaR4rtGRtVs7ianUIlv2ik7+nhDWiFF3T7uqqZgRHzp+Ca/sE 3xb6tGWR8AcsvJEDCT1OeHUMhY++OHUGYIMYgqkNrR8fznbL1c6OZ020n3Vhr8ARWzy0 sBjH8htJGPZp2ZiDOb9n04vff1/y2C/6NfW6cD0KezlUowT7EmGTG47Ia9Va4If1USbe tVRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rO0VyFuqIyykIKWwFkFb/s9ob+da8oVyY9E4V4Pm87w=; b=K9MFMcOQO1EEm1DKxkZ2LFk2wt3E/ce7PgaFEMIy+3Wb0TMNdBA/+bny/OMm1t8IY2 LdRtQtw24N4Wz9p1I+kDsihhsgJW8rFCfwOz1GolhFYCwafv9hpNXbnT+d8FNSkqyH/0 P3wNsmRDGtIOJPIkwYLChQ4PSUjyPoojaf/mYHDzAYBNbpY+8cAebRkcCm4i/hGzKoUQ /QROZPOCm8a7Ea3bzSJFdb3VlbWK1mHu81kDPoXHaPWnGk6a3wpamSrUM5lvNuagPJwC Kz82PV3UtQDWXuBF9PJaB8nMW9elnSC46hF6vmIiwK8fLKolR+FSNSTPenrJ8KHLXd1z IxIw== X-Gm-Message-State: AOAM530iQPiu45GWFdIjisUM00/c6ZYWAMOhTNI3IwpUhEqIymFFiuZ+ ak+oXGosKE+RD8W3OT+aOdwUB8D/Lomo+/79eL8= X-Google-Smtp-Source: ABdhPJzQIpeyRc6YGOfq87HzP82bx+hjkJ40BrA/VTYRlEQ4EsS1a/+KI+ogw1wCa7EEU89dHwj6orGaCmDkFos7up0= X-Received: by 2002:a92:c213:: with SMTP id j19mr4348989ilo.40.1593195820623; Fri, 26 Jun 2020 11:23:40 -0700 (PDT) MIME-Version: 1.0 References: <159318112849.29459.4852442286238599577@ietfa.amsl.com> <87d05lwvzh.wl-jch@irif.fr> In-Reply-To: <87d05lwvzh.wl-jch@irif.fr> From: Donald Eastlake Date: Fri, 26 Jun 2020 14:23:29 -0400 Message-ID: To: Juliusz Chroboczek Cc: Babel at IETF Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [babel] Fwd: IETF 108 Online: Early Bird Registration Ends Today! X-BeenThere: babel@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A list for discussion of the Babel Routing Protocol." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jun 2020 18:23:42 -0000 On Fri, Jun 26, 2020 at 1:57 PM Juliusz Chroboczek wrote: > > > Thus, this time, there are fees for remote participation (although I > > believe listening to the audio streaming will still be free). > > Could you please confirm the latter point? If that's not the case, I'd > rather we didn't have a meeting. My understanding is that the fee is for registering to participate via meetecho to get video as well as audio. And there is a waiver program if you can't afford the registration fee. I'll see if I can confirm that audio monitoring is free but all the comments I remember seeing on the IETF discussion list were pushing for it to be free. Thanks, Donald =============================== Donald E. Eastlake 3rd +1-508-333-2270 (cell) 2386 Panoramic Circle, Apopka, FL 32703 USA d3e3e3@gmail.com > Thanks, > > -- Juliusz From nobody Sat Jun 27 15:02:05 2020 Return-Path: X-Original-To: babel@ietf.org Delivered-To: babel@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D612B3A0828; Sat, 27 Jun 2020 15:02:02 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Murray Kucherawy via Datatracker To: "The IESG" Cc: draft-ietf-babel-dtls@ietf.org, babel-chairs@ietf.org, babel@ietf.org, Donald Eastlake X-Test-IDTracker: no X-IETF-IDTracker: 7.5.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Murray Kucherawy Message-ID: <159329532285.23961.12116288483331623753@ietfa.amsl.com> Date: Sat, 27 Jun 2020 15:02:02 -0700 Archived-At: Subject: [babel] Murray Kucherawy's No Objection on draft-ietf-babel-dtls-09: (with COMMENT) X-BeenThere: babel@ietf.org X-Mailman-Version: 2.1.29 List-Id: "A list for discussion of the Babel Routing Protocol." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jun 2020 22:02:03 -0000 Murray Kucherawy has entered the following ballot position for draft-ietf-babel-dtls-09: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-babel-dtls/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Reading the shorter document before the longer one, so I may be missing some important context here. This was pretty easy to read, so nice work. A number of editorial comments and suggestions follow: Section 2: * "... sent over to both unicast ..." -- s/over to both/over both/, right? Section 2.1: * "... intervals, to avoid ..." -- remove the comma * "Nodes SHOULD drop packets that have been reordered ..." -- Why would an implementer not do this? (i.e., why is it only a SHOULD?) Section 2.2: * "... from the Magic byte ..." -- s/Magic/magic/ Section 2.3: * Please expand/explain "TLV" on first use. * Just an aesthetic suggestion: In this sentence... Since Babel over DTLS only protects unicast packets, implementors may implement Babel over DTLS by modifying an implementation of Babel without DTLS support, and replacing any TLV previously sent over multicast with a separate TLV sent over unicast for each neighbour. ...you use "implementors", "implement", and "implementation". Maybe this? Since Babel over DTLS only protects unicast packets, implementors may provide Babel over DTLS by using a variant of Babel without DTLS support, and replacing any TLV previously sent over multicast with a separate TLV sent over unicast for each neighbour. Section 2.5: * Why is the stuff in the first paragraph only SHOULD/RECOMMENDED? (The answer may lie in the second paragraph, but I'm uncertain.) * I suggest that Section 5 should make a backward reference to this section since it talks about mitigation of an attack. Section 2.6: * "A node MAY allow configuration options to allow ..." -- change one of those "allow"s to "permit" From nobody Sun Jun 28 14:18:12 2020 Return-Path: X-Original-To: babel@ietf.org Delivered-To: babel@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4049E3A0F64; Sun, 28 Jun 2020 14:18:11 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: babel@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.5.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: babel@ietf.org Message-ID: <159337909119.13375.17461250385519431767@ietfa.amsl.com> Date: Sun, 28 Jun 2020 14:18:11 -0700 Archived-At: Subject: [babel] I-D Action: draft-ietf-babel-yang-model-06.txt X-BeenThere: babel@ietf.org X-Mailman-Version: 2.1.29 List-Id: "A list for discussion of the Babel Routing Protocol." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jun 2020 21:18:11 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Babel routing protocol WG of the IETF. Title : YANG Data Model for Babel Authors : Mahesh Jethanandani Barbara Stark Filename : draft-ietf-babel-yang-model-06.txt Pages : 38 Date : 2020-06-28 Abstract: This document defines a data model for the Babel routing protocol. The data model is defined using the YANG data modeling language. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-babel-yang-model-06 https://datatracker.ietf.org/doc/html/draft-ietf-babel-yang-model-06 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-babel-yang-model-06 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sun Jun 28 14:22:51 2020 Return-Path: X-Original-To: babel@ietfa.amsl.com Delivered-To: babel@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 869EF3A0F68 for ; Sun, 28 Jun 2020 14:22:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 aeLXwaFbo-qu for ; Sun, 28 Jun 2020 14:22:49 -0700 (PDT) Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47EBB3A0F67 for ; Sun, 28 Jun 2020 14:22:49 -0700 (PDT) Received: by mail-pl1-x62c.google.com with SMTP id 35so6309612ple.0 for ; Sun, 28 Jun 2020 14:22:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=jvBiPF6UqaRROgUEFVxkKfBB2M8AftFQYL/mxcA4+Go=; b=E+BGwD5LaH0OPFSVygnyoIFOZzBfD5rS6jXCyRzijeUjAp/nRPf7ew/tQogr5vLpJl ZNC1Kj7liVB2sjornbtowj22/Sa2tUCfX3P8qXg0LeKYCSJGrRgo+jMAkWCnnK9Z+T8W iPDXgAfYQoclgqe3bg0Gr0hLcvPJh2PaWa+NukQi6sLGJMQ0OwVRaTVBY/YXHVSeZNxu yDXucZ6CLUmjnDcc40k6tTAbapzdhquq17VJIWdOxMAmTUVQ3jIU7p8B6XlFrraMt5Vs YRL2O37ipA4vj7Hg/h3WI3OzC+coxsQXDFWQxlsAfIjRugFDTit1UwQOTkUB1+a9rRy4 CfeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=jvBiPF6UqaRROgUEFVxkKfBB2M8AftFQYL/mxcA4+Go=; b=dfydWT9xQPUV4q82wumeRurxwmjQN+EjSiEY4UJgYjQGSVbf3qpzvxnh7i5Ak6FeYv +ekL02JelmnNT166eWS2W8npM+/e/7N+XQLZhhFL2sUB+TlrPwPrZm5lKtgLMX3idRoZ WF2XBRUP1OaSqAiE1tn7jlu344AGSH7pWXW6XXDTbOr6fRtqxEbAyr6vcML8hVgBkPGK n1I/Q/sY5eebm02ulvgtInkX4EMu/cxVX4uM6jNp86ldzj5w4I8Zlm2wkQuMImwlkylM Pumie0h8LOuGL2vIbwgx3Rfk0dwYmo4y51Uxhu0PS8qTWKj6rCWhUFtLUp/YmFsL9FGi 2lmw== X-Gm-Message-State: AOAM530JOjdQ4CXQf0M1+w+1VLinicq+7VAiLG+prS+5ghI3tTcJYHwL 6OfQDtGpTYg+mE9z+21WBYxw8iB0 X-Google-Smtp-Source: ABdhPJxSzt9aQraWKKuUq1jtCS+zveJRNsfHLWgZKQGvrhkmZ6EjOp91prYI3MK5hvapI+5ogEnyVw== X-Received: by 2002:a17:90a:d910:: with SMTP id c16mr3807057pjv.136.1593379368072; Sun, 28 Jun 2020 14:22:48 -0700 (PDT) Received: from ?IPv6:2601:647:5600:5020:b073:5b0c:fb5f:d864? ([2601:647:5600:5020:b073:5b0c:fb5f:d864]) by smtp.gmail.com with ESMTPSA id i7sm28084075pgr.86.2020.06.28.14.22.47 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 28 Jun 2020 14:22:47 -0700 (PDT) From: Mahesh Jethanandani Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.5\)) Date: Sun, 28 Jun 2020 14:22:46 -0700 References: <159337909119.13375.17461250385519431767@ietfa.amsl.com> To: babel@ietf.org In-Reply-To: <159337909119.13375.17461250385519431767@ietfa.amsl.com> Message-Id: X-Mailer: Apple Mail (2.3445.9.5) Archived-At: Subject: Re: [babel] I-D Action: draft-ietf-babel-yang-model-06.txt X-BeenThere: babel@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A list for discussion of the Babel Routing Protocol." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jun 2020 21:22:51 -0000 The draft was expiring and this post extends the life of the draft to = end of the year in the hope that we can close on it before then. Cheers. > On Jun 28, 2020, at 2:18 PM, internet-drafts@ietf.org wrote: >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Babel routing protocol WG of the = IETF. >=20 > Title : YANG Data Model for Babel > Authors : Mahesh Jethanandani > Barbara Stark > Filename : draft-ietf-babel-yang-model-06.txt > Pages : 38 > Date : 2020-06-28 >=20 > Abstract: > This document defines a data model for the Babel routing protocol. > The data model is defined using the YANG data modeling language. >=20 >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-babel-yang-model/ >=20 > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-babel-yang-model-06 > https://datatracker.ietf.org/doc/html/draft-ietf-babel-yang-model-06 >=20 > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-babel-yang-model-06 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 >=20 > _______________________________________________ > babel mailing list > babel@ietf.org > https://www.ietf.org/mailman/listinfo/babel Mahesh Jethanandani mjethanandani@gmail.com From nobody Sun Jun 28 16:11:41 2020 Return-Path: X-Original-To: babel@ietfa.amsl.com Delivered-To: babel@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 141903A0FAE for ; Sun, 28 Jun 2020 16:11:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.848 X-Spam-Level: X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 tKb6bmVDLGNn for ; Sun, 28 Jun 2020 16:11:38 -0700 (PDT) Received: from mail-il1-x131.google.com (mail-il1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1CF23A0FAD for ; Sun, 28 Jun 2020 16:11:38 -0700 (PDT) Received: by mail-il1-x131.google.com with SMTP id e18so2257699ilr.7 for ; Sun, 28 Jun 2020 16:11:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xL4FfrNov3jWBzap1KokSABEhtBuMQaW3+x4LBkO16g=; b=loU1tDzekiCHaLr/it3lO5k7xUyi7seyoy1q/LnQECPze01bPk09evnJKTiC2WPSZJ cAVY14KGwBdsOa2KApupTwKsRO2D0BrU/xeEFzPTwu3zL2tldGj/RLDO+gA6HSWYk/WK 37ZTr9yni/+AKw75XmXUP+dHsQkaB/wxaGICPSBopuH+7GNhdwYWomSlZmIJhPfah2MP De7dVmtHOZG8J3pNUZo9RlOQKQd3k5sFj8t528npfBlj6dcIEeZtbAb22+jFgHeM8eJC vtMsVSPNqmocLUo9SZubUQjlp9JjmMgAJzDA9/U6jCTg6D2wREDA6ziH2/52s37cY93y NaAA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xL4FfrNov3jWBzap1KokSABEhtBuMQaW3+x4LBkO16g=; b=fygKnKrfz8rRlqDdqRMfoBPtOxR7QnoFlh2o5YrK/W6xlYJZBb3oCXr81Pr0PfU9TO HmDYFBoUqCstPE3K2n9KzV8BmCkrXDVIk6da0i5Wveg/S/ozPr5S0OK2uHADTq3HNWJT SVMrUAwFRvgEyJDG72x6YY32nGlaKhfGL4Jeaw7rjxI41I4bCOdgQzSbr0tEpb+u7J3c tqEUIQw8/lDybS3g/guXAOy9uvHkeaqxAtoLidb1HTf17XKPLQmc+o1t7HsPi513MdOI fpK0ZcitATDo9E6fFQUk1gZhP1E3wWNUd5aZ1ZzPge7yztTRjAtxzlG1O/a0e71ZWL1W 1mtw== X-Gm-Message-State: AOAM5309LrgTLc4dQTqRl0WSEIXzzdDaVf2T5rhYT0nr6Oip1PK9ZmgL hbAGTndQrq1llFRJ0h+adAAM/ePKOSQ8VALoNspGHsTqPaY= X-Google-Smtp-Source: ABdhPJx5x1txh1mewub6WjMlen1g6uC4ZXGmLrQH67XkcP9bT9r3TmmCaJhUUiO01z6iZE1TSCjp9uIDGbhXXFo6wsM= X-Received: by 2002:a05:6e02:d4c:: with SMTP id h12mr14139033ilj.168.1593385897707; Sun, 28 Jun 2020 16:11:37 -0700 (PDT) MIME-Version: 1.0 References: <159318112849.29459.4852442286238599577@ietfa.amsl.com> <87d05lwvzh.wl-jch@irif.fr> In-Reply-To: From: Donald Eastlake Date: Sun, 28 Jun 2020 19:11:26 -0400 Message-ID: To: Babel at IETF Cc: Juliusz Chroboczek Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [babel] Fwd: IETF 108 Online: Early Bird Registration Ends Today! X-BeenThere: babel@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A list for discussion of the Babel Routing Protocol." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jun 2020 23:11:40 -0000 This to confirm that listening to the audio for IETF-108 will be free. See https://mailarchive.ietf.org/arch/msg/ietf/fdE4G8xJtfQgvPNRFNgdsKd4lTY/ Thanks, Donald =============================== Donald E. Eastlake 3rd +1-508-333-2270 (cell) 2386 Panoramic Circle, Apopka, FL 32703 USA d3e3e3@gmail.com On Fri, Jun 26, 2020 at 2:23 PM Donald Eastlake wrote: > On Fri, Jun 26, 2020 at 1:57 PM Juliusz Chroboczek wrote: > > > > > Thus, this time, there are fees for remote participation (although I > > > believe listening to the audio streaming will still be free). > > > > Could you please confirm the latter point? If that's not the case, I'd > > rather we didn't have a meeting. > > My understanding is that the fee is for registering to participate via > meetecho to get video as well as audio. And there is a waiver program > if you can't afford the registration fee. I'll see if I can confirm > that audio monitoring is free but all the comments I remember seeing > on the IETF discussion list were pushing for it to be free. > > Thanks, > Donald > =============================== > Donald E. Eastlake 3rd +1-508-333-2270 (cell) > 2386 Panoramic Circle, Apopka, FL 32703 USA > d3e3e3@gmail.com > > > Thanks, > > -- Juliusz From nobody Sun Jun 28 19:49:04 2020 Return-Path: X-Original-To: babel@ietfa.amsl.com Delivered-To: babel@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 240B83A03EA; Sun, 28 Jun 2020 19:49:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.848 X-Spam-Level: X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 R5wQuZTnUwLM; Sun, 28 Jun 2020 19:49:01 -0700 (PDT) Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F014C3A02BE; Sun, 28 Jun 2020 19:48:57 -0700 (PDT) Received: by mail-io1-xd2e.google.com with SMTP id f23so15607102iof.6; Sun, 28 Jun 2020 19:48:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lF/3B+8ZcLONpdx9b14O2nWJiUwZpERBkSLn2lbLHjI=; b=Ax0wHYGwAygg0KoBiwM5QO7eCnU2yLn+oHvicBoFMR2gZVZpYRiezz8G11VZZ0HPot rbv5gCtY+36GlFhjujnQ1ZN+qDrpEoxfu5aT5BYVd1/JdzlKWCj88fAyjLSmh2/lerSE pMiOFMDSDURGrXRIHwKxvdhTFsuFzjSfAfwOikmYArbCRU9YYVbtmIlo+kugmlWsiIuJ jF1n0mjTnCwo856kDaBkGN6Lx1Osc+Fv4lMWJ+jPGsE1tFekOihGiq8OjJfOeb7DCcWZ RZDwcZxUTL680o+5XLlaF2VsZBbQqrfZQVw4QzmhI9ejAwu415qQ971CGd4M4CN9Zsca O/iw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lF/3B+8ZcLONpdx9b14O2nWJiUwZpERBkSLn2lbLHjI=; b=sRJiSIu6Qvf9ihfss2Eylr1WxYfzHaR7BulFE/5G0ZJuRrAO0R2n6uQHNG428mB6XH okhRcxKgsHxU/pNB9cRuUlN7RNsDQYg7f5u2S/AtipszqkpMOTv/ygwxyC8KTm3SfViz 2cotGSOtUYFIQzEBMdzPwkqpy7m9UqEfxObA6p5Y6v0z79ngP20TTmAzikPhtK7CuyCh m7P50ZwIPsZ4qBXJE5JzTG1XkRRHknRW1MPd2cIzGVzVH1LW8CJdoYl17E43tMGTA8gD ZoECyV85cBvyvLlw9w6QgLajbIfjKpwSJkdTWH574oX+KQzFv3QHyxVmbyEQ0DhyeiNd JckA== X-Gm-Message-State: AOAM533FEV0XZIrDdOjYT2Vda0nuu/O9+dwYmKMZfI9WowAc9zFTC2tP S7WpjrgIOpGy6jcA1QQUmNp86kcVQD37Hrsdcf5F4RSC X-Google-Smtp-Source: ABdhPJxVKleh1AWQ424xBRJ51r2gjWl2ME00YatEwL4oJSPWVbra1Ilv98MiDaJNgszd37dLQEgU1+HLANYqZWGX3GM= X-Received: by 2002:a02:c043:: with SMTP id u3mr15803429jam.39.1593398936583; Sun, 28 Jun 2020 19:48:56 -0700 (PDT) MIME-Version: 1.0 References: <159011500281.4989.18385341857739016565@ietfa.amsl.com> In-Reply-To: <159011500281.4989.18385341857739016565@ietfa.amsl.com> From: Donald Eastlake Date: Sun, 28 Jun 2020 22:48:45 -0400 Message-ID: To: Babel at IETF Cc: babel-chairs Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [babel] babel - New Meeting Session Request for IETF 108 X-BeenThere: babel@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A list for discussion of the Babel Routing Protocol." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2020 02:49:02 -0000 The Babel session at IETF-108 has been tentatively scheduled for Monday, July 27, 13:00 to 13:50 UTC. Thanks, Donald =============================== Donald E. Eastlake 3rd +1-508-333-2270 (cell) 2386 Panoramic Circle, Apopka, FL 32703 USA d3e3e3@gmail.com On Thu, May 21, 2020 at 10:36 PM IETF Meeting Session Request Tool wrote: > > > > A new meeting session request has just been submitted by Donald E. Eastlake 3rd, a Chair of the babel working group. > > > --------------------------------------------------------- > Working Group Name: Babel routing protocol > Area Name: Routing Area > Session Requester: Donald Eastlake > > > Number of Sessions: 1 > Length of Session(s): 50 Minutes > Number of Attendees: 21 > Conflicts to Avoid: > Chair Conflict: bess idr rtgwg nvo3 > Technology Overlap: homenet manet rtgarea lpwan > Key Participant Conflict: netconf netmod > > > > > > People who must be present: > Donald E. Eastlake 3rd > Russ White > Martin Vigoureux > > Resources Requested: > > Special Requests: > > --------------------------------------------------------- > > From nobody Mon Jun 29 10:49:23 2020 Return-Path: X-Original-To: babel@ietfa.amsl.com Delivered-To: babel@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DC023A089B for ; Mon, 29 Jun 2020 10:49:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 U5BgTLhVNgqP for ; Mon, 29 Jun 2020 10:49:19 -0700 (PDT) Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96A1D3A0858 for ; Mon, 29 Jun 2020 10:49:19 -0700 (PDT) Received: by mail-pl1-x62f.google.com with SMTP id bj10so2150839plb.11 for ; Mon, 29 Jun 2020 10:49:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:message-id:date:to; bh=MuYDmGEVq1jsOvd89/jIEIFm60o+nP1FupNy9r4W30o=; b=pztBe1V1r81SuEtb/o1Ab3zLkNkUg5jB5bMrxZzZ4cG51HMOrpihtIdKK7OnMGUoZT JgwI2zX49UTkCWbv1gLGlm0RGm4tVGbuyYZLooSg3DZcmvQpdOc4X4EqdGcQyIC1x+Sb mnzeRNP4ACdfO4whzAnYXxOhxvfBCpVFWGVYAfST6/piQISP5VlgghZfkcHJgy5QyOho R+OX0NsRr/nv44Tuvmuuw9Rt8KwDntdTQwPRywK957XZVMTLKcLo5w2dSUiZA41AE1rx Xk1UBusZWfrzAFu0baAgt8hgE7gUq5ujAWsy5+yfiqS8sTEVMknLb702af5hQd7S9otG 4qVg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=MuYDmGEVq1jsOvd89/jIEIFm60o+nP1FupNy9r4W30o=; b=O1jbv5nZ/cRU+fnsDCs3giojBl5c7nvgJv9RttfHJzg7PcjLET3hBF+vyVdgtEC+Mq Hgbut6mu7Cs5R9GAWcFmWEUsdsBwd5cgT1YcoW5Zbng5ZqiWUobP+xrFckMWnbB6HlK8 1Aapt/45vR8Pt+t8ozguTCm00QewVt3kDe9CaFXOcW5C9Mmj7mL1pMVDAp9naq3rzZNW 82vO17hw2WLkqaRWPdYPd4w56j792JNlhculKstyys+l7zWVdw8bZUMNZBlRsJ12+nfN JH54MjNW3WdIqoWFk3tKLfzstiDU7yBzWTQGATC9U1RK0SlxY332ymty8RjjwsoLWtNU 9Gsw== X-Gm-Message-State: AOAM5318udU3vB1vA7+BDj3rMvsGllMlpgc5rMrjc7FtkW5Op0as1O0h AOWBPGZBrEDlBAMw7lbPsiTWlc3h X-Google-Smtp-Source: ABdhPJxPA/JbPXwEKFug90BMDq/YK0iLI7jeWkpA7kYSSA1jrc/hnAjax4RlGC3BISHBdN2NZfTOvw== X-Received: by 2002:a17:90a:2367:: with SMTP id f94mr19061402pje.20.1593452958751; Mon, 29 Jun 2020 10:49:18 -0700 (PDT) Received: from ?IPv6:2601:647:5600:5020:f93a:fe27:ee07:acd0? ([2601:647:5600:5020:f93a:fe27:ee07:acd0]) by smtp.gmail.com with ESMTPSA id b10sm320084pft.59.2020.06.29.10.49.18 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Jun 2020 10:49:18 -0700 (PDT) From: Mahesh Jethanandani Content-Type: multipart/alternative; boundary="Apple-Mail=_FA3DCEB8-78CC-4FEE-A505-C86D7009C049" Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.5\)) Message-Id: <306B3968-3A40-4E8C-B29D-72CD8E06873B@gmail.com> Date: Mon, 29 Jun 2020 10:49:17 -0700 To: Babel at IETF X-Mailer: Apple Mail (2.3445.9.5) Archived-At: Subject: [babel] Issue#15: Add support for routing policy X-BeenThere: babel@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A list for discussion of the Babel Routing Protocol." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2020 17:49:21 -0000 --Apple-Mail=_FA3DCEB8-78CC-4FEE-A505-C86D7009C049 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Babel WG, I hope this issue has not been brought up already. In either case, I do = not remember what the resolution was. So here it goes. The issue against the Babel YANG model that I needed to close on is = documented here = . It asks = if Babel needs to add support for extending the base routing policy = model described in draft-ietf-rtgwg-policy-model = . The base = model defined in that document already defines how routes are imported, = exported, or modified across different routing protocols. The idea for = Babel to extend would come if there was a need to extend it further with = conditions (match sets) and actions that the base model cannot or does = not cover. For example, BGP extends the model to add community option = type, to check if the route type is external or internal, etc. Does Babel have a need for operators to be able to extend policy = definition beyond what is already defined in the base model? Cheers. Mahesh Jethanandani mjethanandani@gmail.com --Apple-Mail=_FA3DCEB8-78CC-4FEE-A505-C86D7009C049 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Babel= WG,

I hope this = issue has not been brought up already. In either case, I do not remember = what the resolution was. So here it goes.

The issue against the Babel YANG model = that I needed to close on is documented here. It asks if Babel needs to add support for = extending the base routing policy model described in draft-ietf-rtgwg-policy-model. The base model defined in = that document already defines how routes are imported, exported, or = modified across different routing protocols. The idea for Babel to = extend would come if there was a need to extend it further with = conditions (match sets) and actions that the base model cannot or does = not cover. For example, BGP extends the model to add community option = type, to check if the route type is external or internal, etc.

Does Babel have a need = for operators to be able to extend policy definition beyond what is = already defined in the base model?

Cheers.

Mahesh Jethanandani
mjethanandani@gmail.com



= --Apple-Mail=_FA3DCEB8-78CC-4FEE-A505-C86D7009C049-- From nobody Tue Jun 30 16:00:43 2020 Return-Path: X-Original-To: babel@ietf.org Delivered-To: babel@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A443C3A0964; Tue, 30 Jun 2020 16:00:41 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: babel@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 7.6.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: babel@ietf.org Message-ID: <159355804159.26903.12843532747367653315@ietfa.amsl.com> Date: Tue, 30 Jun 2020 16:00:41 -0700 Archived-At: Subject: [babel] I-D Action: draft-ietf-babel-dtls-10.txt X-BeenThere: babel@ietf.org X-Mailman-Version: 2.1.29 List-Id: "A list for discussion of the Babel Routing Protocol." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2020 23:00:42 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Babel routing protocol WG of the IETF. Title : Babel Routing Protocol over Datagram Transport Layer Security Authors : Antonin Decimo David Schinazi Juliusz Chroboczek Filename : draft-ietf-babel-dtls-10.txt Pages : 10 Date : 2020-06-30 Abstract: The Babel Routing Protocol does not contain any means to authenticate neighbours or provide integrity or confidentiality for messages sent between them. This document specifies a mechanism to ensure these properties, using Datagram Transport Layer Security (DTLS). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-babel-dtls/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-babel-dtls-10 https://datatracker.ietf.org/doc/html/draft-ietf-babel-dtls-10 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-babel-dtls-10 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Jun 30 16:02:00 2020 Return-Path: X-Original-To: babel@ietfa.amsl.com Delivered-To: babel@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 888A73A0965; Tue, 30 Jun 2020 16:01:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 Tubs2jW-Yl2B; Tue, 30 Jun 2020 16:01:51 -0700 (PDT) Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F9F13A095F; Tue, 30 Jun 2020 16:01:48 -0700 (PDT) Received: by mail-lf1-x12f.google.com with SMTP id c21so12432316lfb.3; Tue, 30 Jun 2020 16:01:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DcLwoBxSoXRlUIE2x6HM/p3LGjrmVpdHHRLh2uZdvUM=; b=f6xpO55S9i2Mszz9cHnn2QgPWfqc8z/zmd9l+051grXGSI6wil+U3gGimBNqSA3Kd8 ZA/K9NwT1FXktMzH6b4ebyu8umDzzQJum7P7XA6aixJQXDGBPfdifMNQSy6nz1AxafRd B3T4dipKFLe48a6y8De/HzzXyLbRhgspW0+jealexhZiKQCCzFN7unSsMPnpew/rKlee hCpMncZ+0Y9UQNUiZzH5NPz+B0WTcbk1yMR6AgstDYyt9uGEyxU3ZVBZ0C0QQJ7U5WnQ wAj5Sxzjg0t4yTkTCLjECnOkQsO2VYtElEiIZLYdQSmDi00mGPKjXnDyv7A0PtiYeM9H UWzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DcLwoBxSoXRlUIE2x6HM/p3LGjrmVpdHHRLh2uZdvUM=; b=mf3FTjqLJCUWcAUlKPYE5drCsAgsnZhmxtXZnBkaHcPdfe/7Cu7UxnHAjFtGFU0lf6 pdXe6jm83S0dX9mFM4br9kssG9HuLs/+hS1tLpPRfMauG4pzvrTf6iRhaQ04q3XLlstA ouaE+vcgUfKcuKPX9+/qm9JHgQT/ilnk9CuXMsOnCvXtidfwOlG7UZ0SBc0UL9pkyTnF PhBciBw4/CQ+smNEHw0HEbpFhTGpDiSG84tDnFAYz2/fpLGqZ0yNAKi6fC08NCMq+E36 TyR7BlecKCp8EVZPOUA3O+Mhwiata29Jg4OxtZ0Izb8/oE/bEWJBAsMvJXgjwrSuNjHZ /xjw== X-Gm-Message-State: AOAM531N0VF1TMcVk6KWt+Wws76nkxwKYpTDAF5UV6raHr3466yovGEf PDEPni0Kz3/S/PdG+OBCXMBq0ANv7/HiJVi1f7U= X-Google-Smtp-Source: ABdhPJzw6AL/FKRReT1KdPyCakt72p+ZE5gN1gOqXVN7xXS6CXL87h7jH9kSukuOBC6lzgqyadqgxjml9gBR1ovsU/o= X-Received: by 2002:ac2:5467:: with SMTP id e7mr13118389lfn.122.1593558106433; Tue, 30 Jun 2020 16:01:46 -0700 (PDT) MIME-Version: 1.0 References: <159329532285.23961.12116288483331623753@ietfa.amsl.com> In-Reply-To: <159329532285.23961.12116288483331623753@ietfa.amsl.com> From: David Schinazi Date: Tue, 30 Jun 2020 16:01:35 -0700 Message-ID: To: Murray Kucherawy Cc: The IESG , draft-ietf-babel-dtls@ietf.org, babel-chairs , Babel at IETF , Donald Eastlake Content-Type: multipart/alternative; boundary="000000000000dceea205a955287e" Archived-At: Subject: Re: [babel] Murray Kucherawy's No Objection on draft-ietf-babel-dtls-09: (with COMMENT) X-BeenThere: babel@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A list for discussion of the Babel Routing Protocol." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jun 2020 23:01:54 -0000 --000000000000dceea205a955287e Content-Type: text/plain; charset="UTF-8" Thanks Murray! I've incorporated your feedback into the document and posted draft-ietf-babel-dtls-10 . More detailed responses inline. David On Sat, Jun 27, 2020 at 3:02 PM Murray Kucherawy via Datatracker < noreply@ietf.org> wrote: > Murray Kucherawy has entered the following ballot position for > draft-ietf-babel-dtls-09: No Objection > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html > for more information about IESG DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-babel-dtls/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Reading the shorter document before the longer one, so I may be missing > some > important context here. > > This was pretty easy to read, so nice work. A number of editorial > comments and > suggestions follow: > > Section 2: > > * "... sent over to both unicast ..." -- s/over to both/over both/, right? > Fixed to "can be sent to both" > Section 2.1: > > * "... intervals, to avoid ..." -- remove the comma > I personally prefer the comma, so I'll let the RFC Editor decide this one. > * "Nodes SHOULD drop packets that have been reordered ..." -- Why would an > implementer not do this? (i.e., why is it only a SHOULD?) > Tracking reordering like this is not a feature that is available in all DTLS stacks. Requiring Babel implementors to add features to DTLS stacks is not a realistic possibility, so we made this a SHOULD. > Section 2.2: > > * "... from the Magic byte ..." -- s/Magic/magic/ > The casing here is consistent with the definition of the Magic field: https://tools.ietf.org/html/draft-ietf-babel-rfc6126bis-17#section-4.2 > Section 2.3: > > * Please expand/explain "TLV" on first use. > TLV is considered a well-known abbreviation by the RFC Editor: https://www.rfc-editor.org/materials/abbrev.expansion.txt We'll let them decide this one. > * Just an aesthetic suggestion: In this sentence... > > Since Babel over DTLS only protects unicast packets, implementors may > implement Babel over DTLS by modifying an implementation of Babel > without DTLS support, and replacing any TLV previously sent over > multicast with a separate TLV sent over unicast for each neighbour. > > ...you use "implementors", "implement", and "implementation". Maybe this? > > Since Babel over DTLS only protects unicast packets, implementors may > provide Babel over DTLS by using a variant of Babel > without DTLS support, and replacing any TLV previously sent over > multicast with a separate TLV sent over unicast for each neighbour. > I do agree that repeating "implement" isn't ideal, but I feel that it more accurately represents what we mean. We'll defer to the RFC Editor. > Section 2.5: > > * Why is the stuff in the first paragraph only SHOULD/RECOMMENDED? (The > answer > may lie in the second paragraph, but I'm uncertain.) > Because it's not required for the correctness or security of the protocol. For example, we do not need to mandate where implementors save their DTLS state. > * I suggest that Section 5 should make a backward reference to this section > since it talks about mitigation of an attack. > Good point. I fixed this by moving the second paragraph to the Security Considerations section. > Section 2.6: > > * "A node MAY allow configuration options to allow ..." -- change one of > those > "allow"s to "permit" > Done. --000000000000dceea205a955287e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks Murray! I've incorporated your feedback in= to
the document and posted=C2=A0draft-ietf-babel-dtls-10.
Mor= e detailed responses inline.

David

<= /div>
O= n Sat, Jun 27, 2020 at 3:02 PM Murray Kucherawy via Datatracker <noreply@ietf.org> wrote:
Murray Kucherawy has entered t= he following ballot position for
draft-ietf-babel-dtls-09: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/s= tatement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-b= abel-dtls/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Reading the shorter document before the longer one, so I may be missing som= e
important context here.

This was pretty easy to read, so nice work.=C2=A0 A number of editorial com= ments and
suggestions follow:

Section 2:

* "... sent over to both unicast ..." -- s/over to both/over both= /, right?

Fixed to "can be sent to= both"
=C2=A0
Section 2.1:

* "... intervals, to avoid ..." -- remove the comma

I personally prefer the comma, so I'll let the R= FC Editor decide this one.
=C2=A0
* "Nodes SHOULD drop packets that have been reordered ..." -- Why= would an
implementer not do this?=C2=A0 (i.e., why is it only a SHOULD?)

Tracking reordering like this is not a feature tha= t is available in all DTLS stacks.
Requiring Babel implementors t= o add features to DTLS stacks is not a realistic
possibility, so = we made this a SHOULD.
=C2=A0
Section 2.2:

* "... from the Magic byte ..." -- s/Magic/magic/

The casing here is consistent with the definition of t= he Magic field:
=C2=A0
Section 2.3:

* Please expand/explain "TLV" on first use.
=
TLV is considered a well-known abbreviation by the RFC Edito= r:
https://www.rfc-editor.org/materials/abbrev.expansion.txt
We'll let them decide this one.
=C2=A0
* Just an aesthetic suggestion: In this sentence...

=C2=A0 =C2=A0Since Babel over DTLS only protects unicast packets, implement= ors may
=C2=A0 =C2=A0implement Babel over DTLS by modifying an implementation of Ba= bel
=C2=A0 =C2=A0without DTLS support, and replacing any TLV previously sent ov= er
=C2=A0 =C2=A0multicast with a separate TLV sent over unicast for each neigh= bour.

...you use "implementors", "implement", and "imple= mentation".=C2=A0 Maybe this?

=C2=A0 =C2=A0Since Babel over DTLS only protects unicast packets, implement= ors may
=C2=A0 =C2=A0provide Babel over DTLS by using a variant of Babel
=C2=A0 =C2=A0without DTLS support, and replacing any TLV previously sent ov= er
=C2=A0 =C2=A0multicast with a separate TLV sent over unicast for each neigh= bour.

I do agree that repeating "i= mplement" isn't ideal, but I feel that it more
accuratel= y represents what we mean. We'll defer to the RFC Editor.
=C2= =A0
Section 2.5:

* Why is the stuff in the first paragraph only SHOULD/RECOMMENDED?=C2=A0 (T= he answer
may lie in the second paragraph, but I'm uncertain.)

Because it's not required for the correctness or secu= rity of the protocol. For example,
we do not need to mandate wher= e=C2=A0implementors=C2=A0save their DTLS state.
=C2=A0
* I suggest that Section 5 should make a backward reference to this section=
since it talks about mitigation of an attack.

Good point. I fixed this by moving the second paragraph to the
=
Security Considerations section.
=C2=A0
Section 2.6:

* "A node MAY allow configuration options to allow ..." -- change= one of those
"allow"s to "permit"

Done.=C2=A0
--000000000000dceea205a955287e--