
From nobody Sun Jun 18 09:07:58 2017
Return-Path: <dieter.sibold@ptb.de>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31B5A12947D for <tictoc@ietfa.amsl.com>; Sun, 18 Jun 2017 09:07:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 oikPLKbg4nYV for <tictoc@ietfa.amsl.com>; Sun, 18 Jun 2017 09:07:52 -0700 (PDT)
Received: from mx1.bs.ptb.de (mx1.bs.ptb.de [IPv6:2001:638:610:bd01::120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 344B912947C for <tictoc@ietf.org>; Sun, 18 Jun 2017 09:07:51 -0700 (PDT)
Received: from smtp-hub.bs.ptb.de (smtpint01.bs.ptb.de [141.25.87.32]) by mx1.bs.ptb.de  with ESMTP id v5IG7nGI011281-v5IG7nGK011281 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 18 Jun 2017 18:07:49 +0200
Received: from lotus.bs.ptb.de (lotus.bs.ptb.de [141.25.85.200]) by smtp-hub.bs.ptb.de (Postfix) with ESMTPS id 72EC03B0786; Sun, 18 Jun 2017 18:07:48 +0200 (CEST)
MIME-Version: 1.0
Sensitivity: 
Importance: Normal
X-Priority: 3 (Normal)
In-Reply-To: 
References: 
From: dieter.sibold@ptb.de
To: ntpwg@lists.ntp.org, tictoc@ietf.org
Message-ID: <OF3257274F.275D18CB-ONC1258143.00589ACA-C1258143.00589AD0@ptb.de>
Date: Sun, 18 Jun 2017 18:07:48 +0200
Content-Type: multipart/alternative; boundary="=_alternative 00589ACEC1258143_="
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/NG5dA8cVIqpMYj9luDLDeb3mZLQ>
Subject: [TICTOC] Minutes from last NTP WG Interim Meeting
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Jun 2017 16:07:56 -0000

--=_alternative 00589ACEC1258143_=
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


Hi all,

here are the minutes from the last virtual NTP interim meeting at 25th May.=
 You may also find it under:
https://www.ietf.org/proceedings/interim-2017-ntp-01/minutes/minutes-interi=
m-2017-ntp-01-201705251500-00

Dieter



NTP WG INTERIM MEETING


25 May 2017, 3 pm UTC

PARTICIPANTS:

Aanchal Malhotra, Ankit Kumar Sinha, Daniel Franke, Danny Meyer, Dave
Mills, Denis Reilly, Dhruv Dhody, Dieter Sibold, Harlan Stenn, Karen
O=E2=80=99Donoghue, Kristof Teichel, Kyle Rose, Miroslav Lichvar, Peter Mey=
er,
Richard Welty, Robert Nay, Robert Annessie, Ronan Flood, Sharon
Goldberg, Steward Bryant, Sue Graves, Tal Mizrahi, Yaakov Stein, Scott
Fluhrer

-   Karen: Presentation of IETF Note Well
-   Nobody opposed to record this meeting



AGENDA


-   Network Time Security
-   BCP
-   Data Minimization
-   Message Authentication Code
-   Extension fields and RefID
-   YANG Data Model
-   AOB



OVERVIEW/SUMMARY/NEXT STEPS FOR THE NTS DOCUMENTS.


draft-ietf-ntp-network-time-security
draft-ietf-ntp-network-time-security

-   Daniel reported on the draft 'draft-ietf-ntp-network-time-security'.
    -   The normative parts of the draft are more or less final.
    -   The Security Consideration section will be extended before the
        next submission.
    -   Daniel plans to submit the changed version by the end of March
        and will request the WGLC for it immediately after. The WGLC
        will cover the draft 'draft-ietf-ntp-network-time-security'
        only. It will not cover the other NTS related specifications.
    -   Summary of the changes:
        -   Reduction of the size of the NTS next protocol negotiation
            record
        -   Changes to the IANA Consideration section
        -   Corrections of some inconsistencies which results from the
            removal of the DLTS packet smuggling
        -   Management of keys and cookies for load balanced servers
-   Karen proposes to give the working group a one week time frame to
    comment on the draft. After that period the the WGLC shall be issued
    if there is no objections against it. She would like to have a
    virtual interim meeting by the end of June to discuss the results
    from the WGLC. Because this interim meeting would take place just
    two weeks before the next IETF meeting all participants agreed to
    not have it.
-   Kristof will update the generic draft
    'draft-ietf-ntp-network-time-security' by the end of June.


Summary

-   Daniel to publish update by 26 May.
-   WG has until 31 May to indicate that the document is NOT ready for
    working group last call (WGLC)
-   If no strong opposition, document will go to WGLC in early June.
-   Kristof will work on updating the generic NTS document by the end of
    June.



BCP: OVERVIEW/SUMMARY/ NEXT STEPS FROM THE WGLC


draft-ietf-ntp-bcp

-   In April Denis submitted an update of the document. The changes were
    based on the comments received during the WGLC period.
-   An additional update of the documents were submitted last Monday
    (version 4), based on some additional feedback. It contains text
    changes for the leap seconds, autokey, anycast sections.
-   Denis points out that even when the document talks about the
    reference implementation it brings up ideas that are applicable to
    other implementations as well.
-   Denis makes clear that all the feedback of the WGLC are incorporated
    into the latest version of the draft.
-   Karen asks if we received feedback that indicates that the draft is
    not ready for publication if this feedback is not incorporated.
-   Denis: Daniel suggested mandatory changes to the autokey section in
    order to approve the document. The draft was updated accordingly.
    This was the only feedback that was requested to be fixed.
-   Daniel indicates no objection to the changes made.
-   Karen: if there are no opposition by tomorrow it can be submitted
    for publication.
-   Karen describes the next steps necessary for publication of the
    document. Next steps include approval by the AD, a IETF Last Call,
    IESG review.
-   Sharon ask for the appropriate time to sum minor comments on the
    draft.
-   Denis ask for a dead line for minor changes.
-   Karen: Minor changes until May 31th.


Summary

-   Update addressing all WGLC comments has been published.
-   WG has until 31 May to indicate that the updated document should NOT
    be forwarded to the IESG.
-   Chairs will forward to IESG in early June if there is no strong
    opposition.



WAY FORWARD FOR


draft-dfranke-ntp-data-minimization-02

-   Karen: There have been no objections to adopt this draft. It will be
    approved as a WG document
-   Daniel will submit a new version of the draft. It will contain a
    change regarding the precision field which was requested by Harlan.
-   Sharon points out that with regard to data minimization it makes
    sense to also minimize the information leak in the refid field.
    Together with Harlan she is working on this subject, e.g. in the
    not-you draft. Should this work go into this draft also?
-   Daniel points out that his data minimization draft pertain only to
    client and not server packets. He assumes that his draft and the
    not-you draft are orthogonal.
-   Sharon points out that an adversary can easily request information
    from a server that can be utilized for an attack. Data minimization
    should minimize this also for the server packets. Why mode 1 and
    mode 2 packets are not addressed by the draft?
-   Daniel: The goals of this draft are to solve the unlinkability issue
    with NTP and strengthened the unpredictability of the origin
    timestamp.
-   Sharon: NTP is a hierarchical protocol. Clients may also be server.
    Therefore, data minimization should consider client and server
    packets also.
-   Daniel will submit the new version of his draft and will wait for
    further comments about what should go into it.
-   Harlan expresses that it is fine to allow this draft to be applied
    in WAN environments but it should not be required to be applied in
    LAN environments. As Daniel points out, this draft requires only
    that a server must not reject packets which comply with this
    document. There are no additional hard requirments.
-   Karen: The time line for this document is about one month to do an
    initial review before a WGLC is issued. Next steps will be discussed
    during the Prag meeting.


Summary

-   Adopted as a WG document, Daniel will publish as a wg document
-   Working group will have about a month to review, if no major issues
    identified will proceed to WGLC in early July.



WAY FORWARD FOR


draft-ietf-ntp-mac-00

-   Aanchal reports that there were no comments or objections to this
    draft. Consequently, there are no changes. She recommend to issue a
    WGLC for it.
-   Karen: This is a short and straight forward draft. She would like to
    issue a WGLC. Any objections should be placed before 31th May.
-   No opposition.
-   Short discussion about agility of applied algorithms between Danny,
    Harlan and Karen.
-   Daniel: no objections for WGLC. He will place an feedback during
    WGLC.


Summary

-   Document is stds track updating RFC 5905
-   WG has until 31 May to indicate that the document is NOT ready for
    working group last call (WGLC)
-   If no strong opposition, document will go to WGLC in early June



WAY FORWARD FOR DRAFTS RELATED TO EXTENSION FIELDS AND REFID STUFF


draft-ietf-ntp-refid-updates
draft-stenn-ntp-suggest-refid
draft-stenn-ntp-i-do

-   Karen: There has been a lot of discussion which of the drafts should
    go on and which should be combined.
-   Danny suggest only to publish one refid draft only.
-   Harlan opposes. He already combined different refid drafts.
-   The refid-update draft is moving forward although it is currently
    expired (Sharon is working on this draft)
-   Sharon regards the not-you-refid draft as very important especially
    in the context of data minimization and unlinkability (it will be
    re-submitted by Harlan and Sharon)
-   Karen asks Harlan to submit a roadmap for the extension field and
    refid drafts to the WG, so that the WG knows what is currently on
    the agenda.
-   Tal supports Karen's suggestion to separate new features from RFC
    7822bis. In case we decide to do a RFC 7822bis he proposes to use
    'pseudo code' to clarify the changes.
-   Karen supports Tal's suggestion.
-   Harlan opens the discussion of having a single documents for each
    extension field or one document for all extension fields.
    -   Daniel opposes to both extremes. He suggest to combine logically
        related extension fields into a single document. Like for
        example NTS.
    -   Karen points at that set of extension fields may be publish as
        single RFCs and over time these RFCs can be rolled into a master
        documents.
    -   Daniel suggest that such an consolidation should be done with a
        new NTP version.
    -   At this point Karen interrupts this discussion. The rules of the
        consolidations can be defined later.
-   Karen reiterates that documents should be re-submitted for the
    meeting in Prag.


Summary

-   Harlan/Sharon will republish
    https://datatracker.ietf.org/doc/draft-ietf-ntp-refid-updates/
-   Harlan will provide a summary/roadmap for the remaining expired
    drafts (near term plan)
-   Harlan/Danny will insure that
    https://datatracker.ietf.org/doc/draft-mayer-ntp-mac-extension-field/
    is covered somewhere



OVERVIEW/SUMMARY/NEXT STEPS FOR THE YANG MODEL


draft-wu-ntp-ntp-cfg

-   Ankit presents changes in the YANG data model between version 2 and
    3 of the draft. The changes are (details see presentation:
    https://www.ietf.org/proceedings/interim-2017-ntp-01/slides/slides-inte=
rim-2017-ntp-01-sessa-a-yang-data-model-for-ntp-00.pdf)
    -   Yang tree rearranged as per
    -   NTP Interface
    -   Use of presence
    -   Yang Data-type correction
    -   Removed autokey
-   No changs to the peer mode.
-   Ankit asks for WG adoption and more review comments
-   Danny points out a problem with the Yang date and time format of
    timestamps. NTP timestamps are 64 bit decimal. They are data no
    timestamps.
    -   Tal supports the usage of decimal. Date and time does not make
        sense in this case.
    -   Dhruv suggest to use both date and time and probably decimal.
        From the management point of view it would be helpful to have
        also data and time. They will clarify this.
-   The Yang Model must be adjusted if new extension fields are
    published.
-   Harlan ask for the concept of authorization. YANG and Netconf have a
    security concept for authorization, which is not yet adopted. This
    can and should be done in future versions.
-   No opposition to adopt this as a WG document.


Summary

-   Karen will issue a WG call for adoption of the draft



AOB


-   Danny: will revises the mac-extension-field draft. Harlan indicates
    that this is already incorporated by Harlan in one of his drafts.
-   Denis: TICTOC staff: What is the status of the Enterprise profile?
    -   Karen: the plan is to publish the draft. She will remind Doug to
        proceed with it.
-   Kyle: ask for the purpose of the draft-ietf-ntp-mac draft because
    there is not much normative language. It should be more descriptive.
    It also needs test vectors.
    -   Aanachal makes clear that the main purpose of this draft is do
        deprecate the MD5 legacy MAC. To use it for NTP packets it needs
        more descriptive language.
    -   The draft 'draft-ietf-ntp-mac' will be a standard track update
        to RFC 5905.


-------------------------------------
Dr. Dieter Sibold
Physikalisch-Technische Bundesanstalt
Q.42 - Serversysteme und Datenhaltung
QM-Verantwortlicher der Stelle IT
Bundesallee 100=20
D-38116 Braunschweig
Tel:    +49-531-592-84 20
E-Mail: dieter.sibold@ptb.de
--=_alternative 00589ACEC1258143_=
Content-Type: text/html; charset=UTF-8
Content-ID: <>
Content-Transfer-Encoding: quoted-printable

<font face=3D"Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size=
=3D"2"><div><font face=3D"Default Monospace, Courier New, Courier, monospac=
e"><br></font></div><div><font face=3D"Default Monospace, Courier New, Cour=
ier, monospace">Hi all,<br></font></div><div><font face=3D"Default Monospac=
e, Courier New, Courier, monospace"><br></font></div><div><font face=3D"Def=
ault Monospace, Courier New, Courier, monospace">here are the minutes from =
the last virtual NTP interim meeting at 25th May. You may also find it unde=
r:</font></div><div><font face=3D"Default Monospace, Courier New, Courier, =
monospace"><a href=3D"https://www.ietf.org/proceedings/interim-2017-ntp-01/=
minutes/minutes-interim-2017-ntp-01-201705251500-00" target=3D"=5Fblank">ht=
tps://www.ietf.org/proceedings/interim-2017-ntp-01/minutes/minutes-interim-=
2017-ntp-01-201705251500-00</a><br></font></div><div><font face=3D"Default =
Monospace, Courier New, Courier, monospace"><br></font></div><div><font fac=
e=3D"Default Monospace, Courier New, Courier, monospace">Dieter</font></div=
><div><font face=3D"Default Monospace, Courier New, Courier, monospace"><br=
></font></div><div><div><font face=3D"Default Monospace, Courier New, Couri=
er, monospace"><br></font></div><div><font face=3D"Default Monospace, Couri=
er New, Courier, monospace"><br></font></div><div><font face=3D"Default Mon=
ospace, Courier New, Courier, monospace">NTP WG INTERIM MEETING</font></div=
><div><font face=3D"Default Monospace, Courier New, Courier, monospace"><br=
></font></div><div><font face=3D"Default Monospace, Courier New, Courier, m=
onospace"><br></font></div><div><font face=3D"Default Monospace, Courier Ne=
w, Courier, monospace">25 May 2017, 3 pm UTC</font></div><div><font face=3D=
"Default Monospace, Courier New, Courier, monospace"><br></font></div><div>=
<font face=3D"Default Monospace, Courier New, Courier, monospace">PARTICIPA=
NTS:</font></div><div><font face=3D"Default Monospace, Courier New, Courier=
, monospace"><br></font></div><div><font face=3D"Default Monospace, Courier=
 New, Courier, monospace">Aanchal Malhotra, Ankit Kumar Sinha, Daniel Frank=
e, Danny Meyer, Dave</font></div><div><font face=3D"Default Monospace, Cour=
ier New, Courier, monospace">Mills, Denis Reilly, Dhruv Dhody, Dieter Sibol=
d, Harlan Stenn, Karen</font></div><div><font face=3D"Default Monospace, Co=
urier New, Courier, monospace">O=E2=80=99Donoghue, Kristof Teichel, Kyle Ro=
se, Miroslav Lichvar, Peter Meyer,</font></div><div><font face=3D"Default M=
onospace, Courier New, Courier, monospace">Richard Welty, Robert Nay, Rober=
t Annessie, Ronan Flood, Sharon</font></div><div><font face=3D"Default Mono=
space, Courier New, Courier, monospace">Goldberg, Steward Bryant, Sue Grave=
s, Tal Mizrahi, Yaakov Stein, Scott</font></div><div><font face=3D"Default =
Monospace, Courier New, Courier, monospace">Fluhrer</font></div><div><font =
face=3D"Default Monospace, Courier New, Courier, monospace"><br></font></di=
v><div><font face=3D"Default Monospace, Courier New, Courier, monospace">- =
&nbsp; Karen: Presentation of IETF Note Well</font></div><div><font face=3D=
"Default Monospace, Courier New, Courier, monospace">- &nbsp; Nobody oppose=
d to record this meeting</font></div><div><font face=3D"Default Monospace, =
Courier New, Courier, monospace"><br></font></div><div><font face=3D"Defaul=
t Monospace, Courier New, Courier, monospace"><br></font></div><div><font f=
ace=3D"Default Monospace, Courier New, Courier, monospace"><br></font></div=
><div><font face=3D"Default Monospace, Courier New, Courier, monospace">AGE=
NDA</font></div><div><font face=3D"Default Monospace, Courier New, Courier,=
 monospace"><br></font></div><div><font face=3D"Default Monospace, Courier =
New, Courier, monospace"><br></font></div><div><font face=3D"Default Monosp=
ace, Courier New, Courier, monospace">- &nbsp; Network Time Security</font>=
</div><div><font face=3D"Default Monospace, Courier New, Courier, monospace=
">- &nbsp; BCP</font></div><div><font face=3D"Default Monospace, Courier Ne=
w, Courier, monospace">- &nbsp; Data Minimization</font></div><div><font fa=
ce=3D"Default Monospace, Courier New, Courier, monospace">- &nbsp; Message =
Authentication Code</font></div><div><font face=3D"Default Monospace, Couri=
er New, Courier, monospace">- &nbsp; Extension fields and RefID</font></div=
><div><font face=3D"Default Monospace, Courier New, Courier, monospace">- &=
nbsp; YANG Data Model</font></div><div><font face=3D"Default Monospace, Cou=
rier New, Courier, monospace">- &nbsp; AOB</font></div><div><font face=3D"D=
efault Monospace, Courier New, Courier, monospace"><br></font></div><div><f=
ont face=3D"Default Monospace, Courier New, Courier, monospace"><br></font>=
</div><div><font face=3D"Default Monospace, Courier New, Courier, monospace=
"><br></font></div><div><font face=3D"Default Monospace, Courier New, Couri=
er, monospace">OVERVIEW/SUMMARY/NEXT STEPS FOR THE NTS DOCUMENTS.</font></d=
iv><div><font face=3D"Default Monospace, Courier New, Courier, monospace"><=
br></font></div><div><font face=3D"Default Monospace, Courier New, Courier,=
 monospace"><br></font></div><div><font face=3D"Default Monospace, Courier =
New, Courier, monospace">draft-ietf-ntp-network-time-security</font></div><=
div><font face=3D"Default Monospace, Courier New, Courier, monospace">draft=
-ietf-ntp-network-time-security</font></div><div><font face=3D"Default Mono=
space, Courier New, Courier, monospace"><br></font></div><div><font face=3D=
"Default Monospace, Courier New, Courier, monospace">- &nbsp; Daniel report=
ed on the draft 'draft-ietf-ntp-network-time-security'.</font></div><div><f=
ont face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbs=
p; - &nbsp; The normative parts of the draft are more or less final.</font>=
</div><div><font face=3D"Default Monospace, Courier New, Courier, monospace=
">&nbsp; &nbsp; - &nbsp; The Security Consideration section will be extende=
d before the</font></div><div><font face=3D"Default Monospace, Courier New,=
 Courier, monospace">&nbsp; &nbsp; &nbsp; &nbsp; next submission.</font></d=
iv><div><font face=3D"Default Monospace, Courier New, Courier, monospace">&=
nbsp; &nbsp; - &nbsp; Daniel plans to submit the changed version by the end=
 of March</font></div><div><font face=3D"Default Monospace, Courier New, Co=
urier, monospace">&nbsp; &nbsp; &nbsp; &nbsp; and will request the WGLC for=
 it immediately after. The WGLC</font></div><div><font face=3D"Default Mono=
space, Courier New, Courier, monospace">&nbsp; &nbsp; &nbsp; &nbsp; will co=
ver the draft 'draft-ietf-ntp-network-time-security'</font></div><div><font=
 face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; =
&nbsp; &nbsp; only. It will not cover the other NTS related specifications.=
</font></div><div><font face=3D"Default Monospace, Courier New, Courier, mo=
nospace">&nbsp; &nbsp; - &nbsp; Summary of the changes:</font></div><div><f=
ont face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbs=
p; &nbsp; &nbsp; - &nbsp; Reduction of the size of the NTS next protocol ne=
gotiation</font></div><div><font face=3D"Default Monospace, Courier New, Co=
urier, monospace">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; record</font></=
div><div><font face=3D"Default Monospace, Courier New, Courier, monospace">=
&nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; Changes to the IANA Consideration sect=
ion</font></div><div><font face=3D"Default Monospace, Courier New, Courier,=
 monospace">&nbsp; &nbsp; &nbsp; &nbsp; - &nbsp; Corrections of some incons=
istencies which results from the</font></div><div><font face=3D"Default Mon=
ospace, Courier New, Courier, monospace">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;=
 &nbsp; removal of the DLTS packet smuggling</font></div><div><font face=3D=
"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; &nbsp; &=
nbsp; - &nbsp; Management of keys and cookies for load balanced servers</fo=
nt></div><div><font face=3D"Default Monospace, Courier New, Courier, monosp=
ace">- &nbsp; Karen proposes to give the working group a one week time fram=
e to</font></div><div><font face=3D"Default Monospace, Courier New, Courier=
, monospace">&nbsp; &nbsp; comment on the draft. After that period the the =
WGLC shall be issued</font></div><div><font face=3D"Default Monospace, Cour=
ier New, Courier, monospace">&nbsp; &nbsp; if there is no objections agains=
t it. She would like to have a</font></div><div><font face=3D"Default Monos=
pace, Courier New, Courier, monospace">&nbsp; &nbsp; virtual interim meetin=
g by the end of June to discuss the results</font></div><div><font face=3D"=
Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; from the =
WGLC. Because this interim meeting would take place just</font></div><div><=
font face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nb=
sp; two weeks before the next IETF meeting all participants agreed to</font=
></div><div><font face=3D"Default Monospace, Courier New, Courier, monospac=
e">&nbsp; &nbsp; not have it.</font></div><div><font face=3D"Default Monosp=
ace, Courier New, Courier, monospace">- &nbsp; Kristof will update the gene=
ric draft</font></div><div><font face=3D"Default Monospace, Courier New, Co=
urier, monospace">&nbsp; &nbsp; 'draft-ietf-ntp-network-time-security' by t=
he end of June.</font></div><div><font face=3D"Default Monospace, Courier N=
ew, Courier, monospace"><br></font></div><div><font face=3D"Default Monospa=
ce, Courier New, Courier, monospace"><br></font></div><div><font face=3D"De=
fault Monospace, Courier New, Courier, monospace">Summary</font></div><div>=
<font face=3D"Default Monospace, Courier New, Courier, monospace"><br></fon=
t></div><div><font face=3D"Default Monospace, Courier New, Courier, monospa=
ce">- &nbsp; Daniel to publish update by 26 May.</font></div><div><font fac=
e=3D"Default Monospace, Courier New, Courier, monospace">- &nbsp; WG has un=
til 31 May to indicate that the document is NOT ready for</font></div><div>=
<font face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &n=
bsp; working group last call (WGLC)</font></div><div><font face=3D"Default =
Monospace, Courier New, Courier, monospace">- &nbsp; If no strong oppositio=
n, document will go to WGLC in early June.</font></div><div><font face=3D"D=
efault Monospace, Courier New, Courier, monospace">- &nbsp; Kristof will wo=
rk on updating the generic NTS document by the end of</font></div><div><fon=
t face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp;=
 June.</font></div><div><font face=3D"Default Monospace, Courier New, Couri=
er, monospace"><br></font></div><div><font face=3D"Default Monospace, Couri=
er New, Courier, monospace"><br></font></div><div><font face=3D"Default Mon=
ospace, Courier New, Courier, monospace"><br></font></div><div><font face=
=3D"Default Monospace, Courier New, Courier, monospace">BCP: OVERVIEW/SUMMA=
RY/ NEXT STEPS FROM THE WGLC</font></div><div><font face=3D"Default Monospa=
ce, Courier New, Courier, monospace"><br></font></div><div><font face=3D"De=
fault Monospace, Courier New, Courier, monospace"><br></font></div><div><fo=
nt face=3D"Default Monospace, Courier New, Courier, monospace">draft-ietf-n=
tp-bcp</font></div><div><font face=3D"Default Monospace, Courier New, Couri=
er, monospace"><br></font></div><div><font face=3D"Default Monospace, Couri=
er New, Courier, monospace">- &nbsp; In April Denis submitted an update of =
the document. The changes were</font></div><div><font face=3D"Default Monos=
pace, Courier New, Courier, monospace">&nbsp; &nbsp; based on the comments =
received during the WGLC period.</font></div><div><font face=3D"Default Mon=
ospace, Courier New, Courier, monospace">- &nbsp; An additional update of t=
he documents were submitted last Monday</font></div><div><font face=3D"Defa=
ult Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; (version 4), =
based on some additional feedback. It contains text</font></div><div><font =
face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; c=
hanges for the leap seconds, autokey, anycast sections.</font></div><div><f=
ont face=3D"Default Monospace, Courier New, Courier, monospace">- &nbsp; De=
nis points out that even when the document talks about the</font></div><div=
><font face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &=
nbsp; reference implementation it brings up ideas that are applicable to</f=
ont></div><div><font face=3D"Default Monospace, Courier New, Courier, monos=
pace">&nbsp; &nbsp; other implementations as well.</font></div><div><font f=
ace=3D"Default Monospace, Courier New, Courier, monospace">- &nbsp; Denis m=
akes clear that all the feedback of the WGLC are incorporated</font></div><=
div><font face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp=
; &nbsp; into the latest version of the draft.</font></div><div><font face=
=3D"Default Monospace, Courier New, Courier, monospace">- &nbsp; Karen asks=
 if we received feedback that indicates that the draft is</font></div><div>=
<font face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &n=
bsp; not ready for publication if this feedback is not incorporated.</font>=
</div><div><font face=3D"Default Monospace, Courier New, Courier, monospace=
">- &nbsp; Denis: Daniel suggested mandatory changes to the autokey section=
 in</font></div><div><font face=3D"Default Monospace, Courier New, Courier,=
 monospace">&nbsp; &nbsp; order to approve the document. The draft was upda=
ted accordingly.</font></div><div><font face=3D"Default Monospace, Courier =
New, Courier, monospace">&nbsp; &nbsp; This was the only feedback that was =
requested to be fixed.</font></div><div><font face=3D"Default Monospace, Co=
urier New, Courier, monospace">- &nbsp; Daniel indicates no objection to th=
e changes made.</font></div><div><font face=3D"Default Monospace, Courier N=
ew, Courier, monospace">- &nbsp; Karen: if there are no opposition by tomor=
row it can be submitted</font></div><div><font face=3D"Default Monospace, C=
ourier New, Courier, monospace">&nbsp; &nbsp; for publication.</font></div>=
<div><font face=3D"Default Monospace, Courier New, Courier, monospace">- &n=
bsp; Karen describes the next steps necessary for publication of the</font>=
</div><div><font face=3D"Default Monospace, Courier New, Courier, monospace=
">&nbsp; &nbsp; document. Next steps include approval by the AD, a IETF Las=
t Call,</font></div><div><font face=3D"Default Monospace, Courier New, Cour=
ier, monospace">&nbsp; &nbsp; IESG review.</font></div><div><font face=3D"D=
efault Monospace, Courier New, Courier, monospace">- &nbsp; Sharon ask for =
the appropriate time to sum minor comments on the</font></div><div><font fa=
ce=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; dra=
ft.</font></div><div><font face=3D"Default Monospace, Courier New, Courier,=
 monospace">- &nbsp; Denis ask for a dead line for minor changes.</font></d=
iv><div><font face=3D"Default Monospace, Courier New, Courier, monospace">-=
 &nbsp; Karen: Minor changes until May 31th.</font></div><div><font face=3D=
"Default Monospace, Courier New, Courier, monospace"><br></font></div><div>=
<font face=3D"Default Monospace, Courier New, Courier, monospace"><br></fon=
t></div><div><font face=3D"Default Monospace, Courier New, Courier, monospa=
ce">Summary</font></div><div><font face=3D"Default Monospace, Courier New, =
Courier, monospace"><br></font></div><div><font face=3D"Default Monospace, =
Courier New, Courier, monospace">- &nbsp; Update addressing all WGLC commen=
ts has been published.</font></div><div><font face=3D"Default Monospace, Co=
urier New, Courier, monospace">- &nbsp; WG has until 31 May to indicate tha=
t the updated document should NOT</font></div><div><font face=3D"Default Mo=
nospace, Courier New, Courier, monospace">&nbsp; &nbsp; be forwarded to the=
 IESG.</font></div><div><font face=3D"Default Monospace, Courier New, Couri=
er, monospace">- &nbsp; Chairs will forward to IESG in early June if there =
is no strong</font></div><div><font face=3D"Default Monospace, Courier New,=
 Courier, monospace">&nbsp; &nbsp; opposition.</font></div><div><font face=
=3D"Default Monospace, Courier New, Courier, monospace"><br></font></div><d=
iv><font face=3D"Default Monospace, Courier New, Courier, monospace"><br></=
font></div><div><font face=3D"Default Monospace, Courier New, Courier, mono=
space"><br></font></div><div><font face=3D"Default Monospace, Courier New, =
Courier, monospace">WAY FORWARD FOR</font></div><div><font face=3D"Default =
Monospace, Courier New, Courier, monospace"><br></font></div><div><font fac=
e=3D"Default Monospace, Courier New, Courier, monospace"><br></font></div><=
div><font face=3D"Default Monospace, Courier New, Courier, monospace">draft=
-dfranke-ntp-data-minimization-02</font></div><div><font face=3D"Default Mo=
nospace, Courier New, Courier, monospace"><br></font></div><div><font face=
=3D"Default Monospace, Courier New, Courier, monospace">- &nbsp; Karen: The=
re have been no objections to adopt this draft. It will be</font></div><div=
><font face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &=
nbsp; approved as a WG document</font></div><div><font face=3D"Default Mono=
space, Courier New, Courier, monospace">- &nbsp; Daniel will submit a new v=
ersion of the draft. It will contain a</font></div><div><font face=3D"Defau=
lt Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; change regardi=
ng the precision field which was requested by Harlan.</font></div><div><fon=
t face=3D"Default Monospace, Courier New, Courier, monospace">- &nbsp; Shar=
on points out that with regard to data minimization it makes</font></div><d=
iv><font face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp;=
 &nbsp; sense to also minimize the information leak in the refid field.</fo=
nt></div><div><font face=3D"Default Monospace, Courier New, Courier, monosp=
ace">&nbsp; &nbsp; Together with Harlan she is working on this subject, e.g=
. in the</font></div><div><font face=3D"Default Monospace, Courier New, Cou=
rier, monospace">&nbsp; &nbsp; not-you draft. Should this work go into this=
 draft also?</font></div><div><font face=3D"Default Monospace, Courier New,=
 Courier, monospace">- &nbsp; Daniel points out that his data minimization =
draft pertain only to</font></div><div><font face=3D"Default Monospace, Cou=
rier New, Courier, monospace">&nbsp; &nbsp; client and not server packets. =
He assumes that his draft and the</font></div><div><font face=3D"Default Mo=
nospace, Courier New, Courier, monospace">&nbsp; &nbsp; not-you draft are o=
rthogonal.</font></div><div><font face=3D"Default Monospace, Courier New, C=
ourier, monospace">- &nbsp; Sharon points out that an adversary can easily =
request information</font></div><div><font face=3D"Default Monospace, Couri=
er New, Courier, monospace">&nbsp; &nbsp; from a server that can be utilize=
d for an attack. Data minimization</font></div><div><font face=3D"Default M=
onospace, Courier New, Courier, monospace">&nbsp; &nbsp; should minimize th=
is also for the server packets. Why mode 1 and</font></div><div><font face=
=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; mode =
2 packets are not addressed by the draft?</font></div><div><font face=3D"De=
fault Monospace, Courier New, Courier, monospace">- &nbsp; Daniel: The goal=
s of this draft are to solve the unlinkability issue</font></div><div><font=
 face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; =
with NTP and strengthened the unpredictability of the origin</font></div><d=
iv><font face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp;=
 &nbsp; timestamp.</font></div><div><font face=3D"Default Monospace, Courie=
r New, Courier, monospace">- &nbsp; Sharon: NTP is a hierarchical protocol.=
 Clients may also be server.</font></div><div><font face=3D"Default Monospa=
ce, Courier New, Courier, monospace">&nbsp; &nbsp; Therefore, data minimiza=
tion should consider client and server</font></div><div><font face=3D"Defau=
lt Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; packets also.<=
/font></div><div><font face=3D"Default Monospace, Courier New, Courier, mon=
ospace">- &nbsp; Daniel will submit the new version of his draft and will w=
ait for</font></div><div><font face=3D"Default Monospace, Courier New, Cour=
ier, monospace">&nbsp; &nbsp; further comments about what should go into it=
.</font></div><div><font face=3D"Default Monospace, Courier New, Courier, m=
onospace">- &nbsp; Harlan expresses that it is fine to allow this draft to =
be applied</font></div><div><font face=3D"Default Monospace, Courier New, C=
ourier, monospace">&nbsp; &nbsp; in WAN environments but it should not be r=
equired to be applied in</font></div><div><font face=3D"Default Monospace, =
Courier New, Courier, monospace">&nbsp; &nbsp; LAN environments. As Daniel =
points out, this draft requires only</font></div><div><font face=3D"Default=
 Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; that a server mu=
st not reject packets which comply with this</font></div><div><font face=3D=
"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; document=
. There are no additional hard requirments.</font></div><div><font face=3D"=
Default Monospace, Courier New, Courier, monospace">- &nbsp; Karen: The tim=
e line for this document is about one month to do an</font></div><div><font=
 face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; =
initial review before a WGLC is issued. Next steps will be discussed</font>=
</div><div><font face=3D"Default Monospace, Courier New, Courier, monospace=
">&nbsp; &nbsp; during the Prag meeting.</font></div><div><font face=3D"Def=
ault Monospace, Courier New, Courier, monospace"><br></font></div><div><fon=
t face=3D"Default Monospace, Courier New, Courier, monospace"><br></font></=
div><div><font face=3D"Default Monospace, Courier New, Courier, monospace">=
Summary</font></div><div><font face=3D"Default Monospace, Courier New, Cour=
ier, monospace"><br></font></div><div><font face=3D"Default Monospace, Cour=
ier New, Courier, monospace">- &nbsp; Adopted as a WG document, Daniel will=
 publish as a wg document</font></div><div><font face=3D"Default Monospace,=
 Courier New, Courier, monospace">- &nbsp; Working group will have about a =
month to review, if no major issues</font></div><div><font face=3D"Default =
Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; identified will p=
roceed to WGLC in early July.</font></div><div><font face=3D"Default Monosp=
ace, Courier New, Courier, monospace"><br></font></div><div><font face=3D"D=
efault Monospace, Courier New, Courier, monospace"><br></font></div><div><f=
ont face=3D"Default Monospace, Courier New, Courier, monospace"><br></font>=
</div><div><font face=3D"Default Monospace, Courier New, Courier, monospace=
">WAY FORWARD FOR</font></div><div><font face=3D"Default Monospace, Courier=
 New, Courier, monospace"><br></font></div><div><font face=3D"Default Monos=
pace, Courier New, Courier, monospace"><br></font></div><div><font face=3D"=
Default Monospace, Courier New, Courier, monospace">draft-ietf-ntp-mac-00</=
font></div><div><font face=3D"Default Monospace, Courier New, Courier, mono=
space"><br></font></div><div><font face=3D"Default Monospace, Courier New, =
Courier, monospace">- &nbsp; Aanchal reports that there were no comments or=
 objections to this</font></div><div><font face=3D"Default Monospace, Couri=
er New, Courier, monospace">&nbsp; &nbsp; draft. Consequently, there are no=
 changes. She recommend to issue a</font></div><div><font face=3D"Default M=
onospace, Courier New, Courier, monospace">&nbsp; &nbsp; WGLC for it.</font=
></div><div><font face=3D"Default Monospace, Courier New, Courier, monospac=
e">- &nbsp; Karen: This is a short and straight forward draft. She would li=
ke to</font></div><div><font face=3D"Default Monospace, Courier New, Courie=
r, monospace">&nbsp; &nbsp; issue a WGLC. Any objections should be placed b=
efore 31th May.</font></div><div><font face=3D"Default Monospace, Courier N=
ew, Courier, monospace">- &nbsp; No opposition.</font></div><div><font face=
=3D"Default Monospace, Courier New, Courier, monospace">- &nbsp; Short disc=
ussion about agility of applied algorithms between Danny,</font></div><div>=
<font face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &n=
bsp; Harlan and Karen.</font></div><div><font face=3D"Default Monospace, Co=
urier New, Courier, monospace">- &nbsp; Daniel: no objections for WGLC. He =
will place an feedback during</font></div><div><font face=3D"Default Monosp=
ace, Courier New, Courier, monospace">&nbsp; &nbsp; WGLC.</font></div><div>=
<font face=3D"Default Monospace, Courier New, Courier, monospace"><br></fon=
t></div><div><font face=3D"Default Monospace, Courier New, Courier, monospa=
ce"><br></font></div><div><font face=3D"Default Monospace, Courier New, Cou=
rier, monospace">Summary</font></div><div><font face=3D"Default Monospace, =
Courier New, Courier, monospace"><br></font></div><div><font face=3D"Defaul=
t Monospace, Courier New, Courier, monospace">- &nbsp; Document is stds tra=
ck updating RFC 5905</font></div><div><font face=3D"Default Monospace, Cour=
ier New, Courier, monospace">- &nbsp; WG has until 31 May to indicate that =
the document is NOT ready for</font></div><div><font face=3D"Default Monosp=
ace, Courier New, Courier, monospace">&nbsp; &nbsp; working group last call=
 (WGLC)</font></div><div><font face=3D"Default Monospace, Courier New, Cour=
ier, monospace">- &nbsp; If no strong opposition, document will go to WGLC =
in early June</font></div><div><font face=3D"Default Monospace, Courier New=
, Courier, monospace"><br></font></div><div><font face=3D"Default Monospace=
, Courier New, Courier, monospace"><br></font></div><div><font face=3D"Defa=
ult Monospace, Courier New, Courier, monospace"><br></font></div><div><font=
 face=3D"Default Monospace, Courier New, Courier, monospace">WAY FORWARD FO=
R DRAFTS RELATED TO EXTENSION FIELDS AND REFID STUFF</font></div><div><font=
 face=3D"Default Monospace, Courier New, Courier, monospace"><br></font></d=
iv><div><font face=3D"Default Monospace, Courier New, Courier, monospace"><=
br></font></div><div><font face=3D"Default Monospace, Courier New, Courier,=
 monospace">draft-ietf-ntp-refid-updates</font></div><div><font face=3D"Def=
ault Monospace, Courier New, Courier, monospace">draft-stenn-ntp-suggest-re=
fid</font></div><div><font face=3D"Default Monospace, Courier New, Courier,=
 monospace">draft-stenn-ntp-i-do</font></div><div><font face=3D"Default Mon=
ospace, Courier New, Courier, monospace"><br></font></div><div><font face=
=3D"Default Monospace, Courier New, Courier, monospace">- &nbsp; Karen: The=
re has been a lot of discussion which of the drafts should</font></div><div=
><font face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &=
nbsp; go on and which should be combined.</font></div><div><font face=3D"De=
fault Monospace, Courier New, Courier, monospace">- &nbsp; Danny suggest on=
ly to publish one refid draft only.</font></div><div><font face=3D"Default =
Monospace, Courier New, Courier, monospace">- &nbsp; Harlan opposes. He alr=
eady combined different refid drafts.</font></div><div><font face=3D"Defaul=
t Monospace, Courier New, Courier, monospace">- &nbsp; The refid-update dra=
ft is moving forward although it is currently</font></div><div><font face=
=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; expir=
ed (Sharon is working on this draft)</font></div><div><font face=3D"Default=
 Monospace, Courier New, Courier, monospace">- &nbsp; Sharon regards the no=
t-you-refid draft as very important especially</font></div><div><font face=
=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; in th=
e context of data minimization and unlinkability (it will be</font></div><d=
iv><font face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp;=
 &nbsp; re-submitted by Harlan and Sharon)</font></div><div><font face=3D"D=
efault Monospace, Courier New, Courier, monospace">- &nbsp; Karen asks Harl=
an to submit a roadmap for the extension field and</font></div><div><font f=
ace=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; re=
fid drafts to the WG, so that the WG knows what is currently on</font></div=
><div><font face=3D"Default Monospace, Courier New, Courier, monospace">&nb=
sp; &nbsp; the agenda.</font></div><div><font face=3D"Default Monospace, Co=
urier New, Courier, monospace">- &nbsp; Tal supports Karen's suggestion to =
separate new features from RFC</font></div><div><font face=3D"Default Monos=
pace, Courier New, Courier, monospace">&nbsp; &nbsp; 7822bis. In case we de=
cide to do a RFC 7822bis he proposes to use</font></div><div><font face=3D"=
Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; 'pseudo c=
ode' to clarify the changes.</font></div><div><font face=3D"Default Monospa=
ce, Courier New, Courier, monospace">- &nbsp; Karen supports Tal's suggesti=
on.</font></div><div><font face=3D"Default Monospace, Courier New, Courier,=
 monospace">- &nbsp; Harlan opens the discussion of having a single documen=
ts for each</font></div><div><font face=3D"Default Monospace, Courier New, =
Courier, monospace">&nbsp; &nbsp; extension field or one document for all e=
xtension fields.</font></div><div><font face=3D"Default Monospace, Courier =
New, Courier, monospace">&nbsp; &nbsp; - &nbsp; Daniel opposes to both extr=
emes. He suggest to combine logically</font></div><div><font face=3D"Defaul=
t Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; &nbsp; &nbsp; r=
elated extension fields into a single document. Like for</font></div><div><=
font face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nb=
sp; &nbsp; &nbsp; example NTS.</font></div><div><font face=3D"Default Monos=
pace, Courier New, Courier, monospace">&nbsp; &nbsp; - &nbsp; Karen points =
at that set of extension fields may be publish as</font></div><div><font fa=
ce=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; &nb=
sp; &nbsp; single RFCs and over time these RFCs can be rolled into a master=
</font></div><div><font face=3D"Default Monospace, Courier New, Courier, mo=
nospace">&nbsp; &nbsp; &nbsp; &nbsp; documents.</font></div><div><font face=
=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; - &nb=
sp; Daniel suggest that such an consolidation should be done with a</font><=
/div><div><font face=3D"Default Monospace, Courier New, Courier, monospace"=
>&nbsp; &nbsp; &nbsp; &nbsp; new NTP version.</font></div><div><font face=
=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; - &nb=
sp; At this point Karen interrupts this discussion. The rules of the</font>=
</div><div><font face=3D"Default Monospace, Courier New, Courier, monospace=
">&nbsp; &nbsp; &nbsp; &nbsp; consolidations can be defined later.</font></=
div><div><font face=3D"Default Monospace, Courier New, Courier, monospace">=
- &nbsp; Karen reiterates that documents should be re-submitted for the</fo=
nt></div><div><font face=3D"Default Monospace, Courier New, Courier, monosp=
ace">&nbsp; &nbsp; meeting in Prag.</font></div><div><font face=3D"Default =
Monospace, Courier New, Courier, monospace"><br></font></div><div><font fac=
e=3D"Default Monospace, Courier New, Courier, monospace"><br></font></div><=
div><font face=3D"Default Monospace, Courier New, Courier, monospace">Summa=
ry</font></div><div><font face=3D"Default Monospace, Courier New, Courier, =
monospace"><br></font></div><div><font face=3D"Default Monospace, Courier N=
ew, Courier, monospace">- &nbsp; Harlan/Sharon will republish</font></div><=
div><font face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp=
; &nbsp; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-ntp-refid-u=
pdates/" target=3D"=5Fblank">https://datatracker.ietf.org/doc/draft-ietf-nt=
p-refid-updates/</a></font></div><div><font face=3D"Default Monospace, Cour=
ier New, Courier, monospace">- &nbsp; Harlan will provide a summary/roadmap=
 for the remaining expired</font></div><div><font face=3D"Default Monospace=
, Courier New, Courier, monospace">&nbsp; &nbsp; drafts (near term plan)</f=
ont></div><div><font face=3D"Default Monospace, Courier New, Courier, monos=
pace">- &nbsp; Harlan/Danny will insure that</font></div><div><font face=3D=
"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; <a href=
=3D"https://datatracker.ietf.org/doc/draft-mayer-ntp-mac-extension-field/" =
target=3D"=5Fblank">https://datatracker.ietf.org/doc/draft-mayer-ntp-mac-ex=
tension-field/</a></font></div><div><font face=3D"Default Monospace, Courie=
r New, Courier, monospace">&nbsp; &nbsp; is covered somewhere</font></div><=
div><font face=3D"Default Monospace, Courier New, Courier, monospace"><br><=
/font></div><div><font face=3D"Default Monospace, Courier New, Courier, mon=
ospace"><br></font></div><div><font face=3D"Default Monospace, Courier New,=
 Courier, monospace"><br></font></div><div><font face=3D"Default Monospace,=
 Courier New, Courier, monospace">OVERVIEW/SUMMARY/NEXT STEPS FOR THE YANG =
MODEL</font></div><div><font face=3D"Default Monospace, Courier New, Courie=
r, monospace"><br></font></div><div><font face=3D"Default Monospace, Courie=
r New, Courier, monospace"><br></font></div><div><font face=3D"Default Mono=
space, Courier New, Courier, monospace">draft-wu-ntp-ntp-cfg</font></div><d=
iv><font face=3D"Default Monospace, Courier New, Courier, monospace"><br></=
font></div><div><font face=3D"Default Monospace, Courier New, Courier, mono=
space">- &nbsp; Ankit presents changes in the YANG data model between versi=
on 2 and</font></div><div><font face=3D"Default Monospace, Courier New, Cou=
rier, monospace">&nbsp; &nbsp; 3 of the draft. The changes are (details see=
 presentation:</font></div><div><font face=3D"Default Monospace, Courier Ne=
w, Courier, monospace">&nbsp; &nbsp; <a href=3D"https://www.ietf.org/procee=
dings/interim-2017-ntp-01/slides/slides-interim-2017-ntp-01-sessa-a-yang-da=
ta-model-for-ntp-00.pdf)" target=3D"=5Fblank">https://www.ietf.org/proceedi=
ngs/interim-2017-ntp-01/slides/slides-interim-2017-ntp-01-sessa-a-yang-data=
-model-for-ntp-00.pdf)</a></font></div><div><font face=3D"Default Monospace=
, Courier New, Courier, monospace">&nbsp; &nbsp; - &nbsp; Yang tree rearran=
ged as per</font></div><div><font face=3D"Default Monospace, Courier New, C=
ourier, monospace">&nbsp; &nbsp; - &nbsp; NTP Interface</font></div><div><f=
ont face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbs=
p; - &nbsp; Use of presence</font></div><div><font face=3D"Default Monospac=
e, Courier New, Courier, monospace">&nbsp; &nbsp; - &nbsp; Yang Data-type c=
orrection</font></div><div><font face=3D"Default Monospace, Courier New, Co=
urier, monospace">&nbsp; &nbsp; - &nbsp; Removed autokey</font></div><div><=
font face=3D"Default Monospace, Courier New, Courier, monospace">- &nbsp; N=
o changs to the peer mode.</font></div><div><font face=3D"Default Monospace=
, Courier New, Courier, monospace">- &nbsp; Ankit asks for WG adoption and =
more review comments</font></div><div><font face=3D"Default Monospace, Cour=
ier New, Courier, monospace">- &nbsp; Danny points out a problem with the Y=
ang date and time format of</font></div><div><font face=3D"Default Monospac=
e, Courier New, Courier, monospace">&nbsp; &nbsp; timestamps. NTP timestamp=
s are 64 bit decimal. They are data no</font></div><div><font face=3D"Defau=
lt Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; timestamps.</f=
ont></div><div><font face=3D"Default Monospace, Courier New, Courier, monos=
pace">&nbsp; &nbsp; - &nbsp; Tal supports the usage of decimal. Date and ti=
me does not make</font></div><div><font face=3D"Default Monospace, Courier =
New, Courier, monospace">&nbsp; &nbsp; &nbsp; &nbsp; sense in this case.</f=
ont></div><div><font face=3D"Default Monospace, Courier New, Courier, monos=
pace">&nbsp; &nbsp; - &nbsp; Dhruv suggest to use both date and time and pr=
obably decimal.</font></div><div><font face=3D"Default Monospace, Courier N=
ew, Courier, monospace">&nbsp; &nbsp; &nbsp; &nbsp; From the management poi=
nt of view it would be helpful to have</font></div><div><font face=3D"Defau=
lt Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; &nbsp; &nbsp; =
also data and time. They will clarify this.</font></div><div><font face=3D"=
Default Monospace, Courier New, Courier, monospace">- &nbsp; The Yang Model=
 must be adjusted if new extension fields are</font></div><div><font face=
=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; publi=
shed.</font></div><div><font face=3D"Default Monospace, Courier New, Courie=
r, monospace">- &nbsp; Harlan ask for the concept of authorization. YANG an=
d Netconf have a</font></div><div><font face=3D"Default Monospace, Courier =
New, Courier, monospace">&nbsp; &nbsp; security concept for authorization, =
which is not yet adopted. This</font></div><div><font face=3D"Default Monos=
pace, Courier New, Courier, monospace">&nbsp; &nbsp; can and should be done=
 in future versions.</font></div><div><font face=3D"Default Monospace, Cour=
ier New, Courier, monospace">- &nbsp; No opposition to adopt this as a WG d=
ocument.</font></div><div><font face=3D"Default Monospace, Courier New, Cou=
rier, monospace"><br></font></div><div><font face=3D"Default Monospace, Cou=
rier New, Courier, monospace"><br></font></div><div><font face=3D"Default M=
onospace, Courier New, Courier, monospace">Summary</font></div><div><font f=
ace=3D"Default Monospace, Courier New, Courier, monospace"><br></font></div=
><div><font face=3D"Default Monospace, Courier New, Courier, monospace">- &=
nbsp; Karen will issue a WG call for adoption of the draft</font></div><div=
><font face=3D"Default Monospace, Courier New, Courier, monospace"><br></fo=
nt></div><div><font face=3D"Default Monospace, Courier New, Courier, monosp=
ace"><br></font></div><div><font face=3D"Default Monospace, Courier New, Co=
urier, monospace"><br></font></div><div><font face=3D"Default Monospace, Co=
urier New, Courier, monospace">AOB</font></div><div><font face=3D"Default M=
onospace, Courier New, Courier, monospace"><br></font></div><div><font face=
=3D"Default Monospace, Courier New, Courier, monospace"><br></font></div><d=
iv><font face=3D"Default Monospace, Courier New, Courier, monospace">- &nbs=
p; Danny: will revises the mac-extension-field draft. Harlan indicates</fon=
t></div><div><font face=3D"Default Monospace, Courier New, Courier, monospa=
ce">&nbsp; &nbsp; that this is already incorporated by Harlan in one of his=
 drafts.</font></div><div><font face=3D"Default Monospace, Courier New, Cou=
rier, monospace">- &nbsp; Denis: TICTOC staff: What is the status of the En=
terprise profile?</font></div><div><font face=3D"Default Monospace, Courier=
 New, Courier, monospace">&nbsp; &nbsp; - &nbsp; Karen: the plan is to publ=
ish the draft. She will remind Doug to</font></div><div><font face=3D"Defau=
lt Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; &nbsp; &nbsp; =
proceed with it.</font></div><div><font face=3D"Default Monospace, Courier =
New, Courier, monospace">- &nbsp; Kyle: ask for the purpose of the draft-ie=
tf-ntp-mac draft because</font></div><div><font face=3D"Default Monospace, =
Courier New, Courier, monospace">&nbsp; &nbsp; there is not much normative =
language. It should be more descriptive.</font></div><div><font face=3D"Def=
ault Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; It also need=
s test vectors.</font></div><div><font face=3D"Default Monospace, Courier N=
ew, Courier, monospace">&nbsp; &nbsp; - &nbsp; Aanachal makes clear that th=
e main purpose of this draft is do</font></div><div><font face=3D"Default M=
onospace, Courier New, Courier, monospace">&nbsp; &nbsp; &nbsp; &nbsp; depr=
ecate the MD5 legacy MAC. To use it for NTP packets it needs</font></div><d=
iv><font face=3D"Default Monospace, Courier New, Courier, monospace">&nbsp;=
 &nbsp; &nbsp; &nbsp; more descriptive language.</font></div><div><font fac=
e=3D"Default Monospace, Courier New, Courier, monospace">&nbsp; &nbsp; - &n=
bsp; The draft 'draft-ietf-ntp-mac' will be a standard track update</font><=
/div><div><font face=3D"Default Monospace, Courier New, Courier, monospace"=
>&nbsp; &nbsp; &nbsp; &nbsp; to RFC 5905.</font></div><div><font face=3D"De=
fault Monospace, Courier New, Courier, monospace"><br></font></div></div><d=
iv><font face=3D"Default Monospace, Courier New, Courier, monospace"><br></=
font></div><div><font face=3D"Default Monospace, Courier New, Courier, mono=
space">-------------------------------------<br></font></div><div><font fac=
e=3D"Default Monospace, Courier New, Courier, monospace">Dr. Dieter Sibold<=
br></font></div><div><font face=3D"Default Monospace, Courier New, Courier,=
 monospace">Physikalisch-Technische Bundesanstalt<br></font></div><div><fon=
t face=3D"Default Monospace, Courier New, Courier, monospace">Q.42 - Server=
systeme und Datenhaltung<br></font></div><div><font face=3D"Default Monospa=
ce, Courier New, Courier, monospace">QM-Verantwortlicher der Stelle IT<br><=
/font></div><div><font face=3D"Default Monospace, Courier New, Courier, mon=
ospace">Bundesallee 100 <br></font></div><div><font face=3D"Default Monospa=
ce, Courier New, Courier, monospace">D-38116 Braunschweig<br></font></div><=
div><font face=3D"Default Monospace, Courier New, Courier, monospace">Tel:&=
nbsp;&nbsp;&nbsp;&nbsp;+49-531-592-84 20<br></font></div><div><div><font fa=
ce=3D"Default Monospace, Courier New, Courier, monospace">E-Mail: <a href=
=3D"mailto:dieter.sibold@ptb.de">dieter.sibold@ptb.de</a></font></div></div=
></font>
--=_alternative 00589ACEC1258143_=--


From nobody Fri Jun 23 15:00:07 2017
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tictoc@ietfa.amsl.com
Delivered-To: tictoc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09BBC129ADA; Fri, 23 Jun 2017 14:59:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 yngt978t22pm; Fri, 23 Jun 2017 14:59:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DC4F12943A; Fri, 23 Jun 2017 14:59:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E6DD9B81B73; Fri, 23 Jun 2017 14:59:33 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tictoc@ietf.org
Message-Id: <20170623215933.E6DD9B81B73@rfc-editor.org>
Date: Fri, 23 Jun 2017 14:59:33 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/1Co5GzrlCLR2yjGQWKS8T_sVPy0>
Subject: [TICTOC] RFC 8173 on Precision Time Protocol Version 2 (PTPv2) Management Information Base
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jun 2017 21:59:59 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8173

        Title:      Precision Time Protocol Version 2 
                    (PTPv2) Management Information Base 
        Author:     V. Shankarkumar, L. Montini,
                    T. Frost, G. Dowd
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2017
        Mailbox:    vinays@cisco.com, 
                    lmontini@cisco.com, 
                    tim.frost@calnexsol.com,
                    greg.dowd@microsemi.com
        Pages:      64
        Characters: 118608
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tictoc-ptp-mib-12.txt

        URL:        https://www.rfc-editor.org/info/rfc8173

        DOI:        10.17487/RFC8173

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in internets based on TCP or IP.
In particular, it defines objects for managing networks using the
Precision Time Protocol (PTP), specified in IEEE Std. 1588-2008.

This memo specifies a MIB module in a manner that is both compliant
to the Structure of Management Information version 2 (SMIv2) and semantically
identical to the peer SMIv1 definitions.

This document is a product of the Timing over IP Connection and Transfer of Clock Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Fri Jun 23 17:11:02 2017
Return-Path: <agenda@ietf.org>
X-Original-To: tictoc@ietf.org
Delivered-To: tictoc@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A41D129B3A; Fri, 23 Jun 2017 17:07:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <tictoc-chairs@ietf.org>, <odonoghue@isoc.org>
Cc: suresh.krishnan@gmail.com, tictoc@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149826282549.7840.276943062507240061.idtracker@ietfa.amsl.com>
Date: Fri, 23 Jun 2017 17:07:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tictoc/mKWIpWNTGBON8qsq_ZeU47aN_og>
Subject: [TICTOC] tictoc - Requested session has been scheduled for IETF 99
X-BeenThere: tictoc@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Timing over IP Connection and Transfer of Clock BOF <tictoc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tictoc>, <mailto:tictoc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tictoc/>
List-Post: <mailto:tictoc@ietf.org>
List-Help: <mailto:tictoc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tictoc>, <mailto:tictoc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jun 2017 00:07:05 -0000

Dear Karen O&#39;Donoghue,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 

tictoc Session 1 (2:00:00)
    Tuesday, Morning Session I 0930-1200
    Room Name: Karlin III size: 60
    ---------------------------------------------
    

Special Note: Joint session with NTP


Request Information:


---------------------------------------------------------
Working Group Name: Timing over IP Connection and Transfer of Clock
Area Name: Internet Area
Session Requester: Karen O&#39;Donoghue

Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 30
Conflicts to Avoid: 
 First Priority: sacm oauth nfvrg bmwg cfrg saag trans mpls detnet




People who must be present:
  Karen O&#39;Donoghue
  Suresh Krishnan
  Yaakov Stein
  Dieter Sibold

Resources Requested:

Special Requests:
  Please schedule a joint meeting with the NTP WG. 
---------------------------------------------------------

