Re: [yang-doctors] [I2nsf] Yangdoctors early review of draft-ietf-i2nsf-nsf-monitoring-data-model-04
Andy Bierman <andy@yumaworks.com> Tue, 02 March 2021 14:55 UTC
Return-Path: <andy@yumaworks.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 732C63A1981 for <yang-doctors@ietfa.amsl.com>; Tue, 2 Mar 2021 06:55:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.787
X-Spam-Level:
X-Spam-Status: No, score=-1.787 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 0iuykBWLe9Mq for <yang-doctors@ietfa.amsl.com>; Tue, 2 Mar 2021 06:55:55 -0800 (PST)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 1FAAF3A1982 for <yang-doctors@ietf.org>; Tue, 2 Mar 2021 06:55:55 -0800 (PST)
Received: by mail-lj1-x22c.google.com with SMTP id a17so24303056ljq.2 for <yang-doctors@ietf.org>; Tue, 02 Mar 2021 06:55:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/WqNanLmqWDruVnIZQreGBo8GE7Cg9lmh0x2wInOqmQ=; b=Fmuu2YUWqnCbaBzhIxdqU6tXxG6UMDBmjIIvf88BHO77HuvPl1g4mYliT/QxT3KYoo ugK3etgCkQJK1+fn4t5t+e5Bs/MDRX+um6aa/xmhoy9a+d8F2jNRQ6WaP3YjtL8IfscS J7UAbyBvgyb+W9Fm9W49OLe8ti8+oW0Wo+zb+P1QnipaC7zkJdFw06XW16RIiEd/xN8k lbcrhekujBFxIc2uddufLyst2xJBqlOhSebEmW6hXJPNfY5Q/nm6+IyxZQYPZPiAjTWP 9htHwsuASlzV32t0O2smua4pLvPw5yoCEsTCfkp2CVVwt/nWruxysA0Qj+Tfugk7bx0b JphA==
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=/WqNanLmqWDruVnIZQreGBo8GE7Cg9lmh0x2wInOqmQ=; b=gtCtOxKlBbbMg4nddL2uS2HeTKR+tz1y2ntQAxkgbTHChtpVrItRCbHAUjcj++kBNX MiPQTJmuOI6v17f93YpyFZERmlH+5Topyv2nwfoJjMNq38QOUYffTRJeGLig1BQON+zO 8/IARvnpAgQrE6kp0W6MT2TRCOOUGojycHsFUDrGNZIMW0h2qd1oBQA2D6oG/KDsEQl/ JtXmhpl5y8r0f/VyX6/ss4JnL48ltF5xekoQo40jWKOZ5JN502LRd/fbGJbRs3rqIPVr i5n3VZYeUmmpHX3TQV98IrpxOvaB6LNlRFB7TpfCh8QKVU0RK16s4omxRJ4758CrvEVM JEqA==
X-Gm-Message-State: AOAM532EwBOYb7iybEdGg3UyIVAgPppo+7MMUQdZeCZDCJJfkumCrf41 yPiJfDuxCi8Y6uGLhjoQUi8VKUbktNirlsVT71B9pw==
X-Google-Smtp-Source: ABdhPJwyfxw5kYrBJlLc6y8lsWHfrDEm8FY0rmyA5kywV7UPGvhJEJBzIhBFz2oxYTVK62pJHwdps44Sw9daiw79gWQ=
X-Received: by 2002:a2e:9157:: with SMTP id q23mr2670451ljg.298.1614696951746; Tue, 02 Mar 2021 06:55:51 -0800 (PST)
MIME-Version: 1.0
References: <160192102291.6633.15935674903085952087@ietfa.amsl.com> <CAPK2DewwLOJnnj1ZEYMSvZB1Hpc-8rY1+-dFvzOkJvrT4X2jqA@mail.gmail.com> <CABCOCHRaSTLDngZnMaQFiq05AZbymJfFFVY+P_fmzuU4e3S7FQ@mail.gmail.com> <01E6A215-B86F-4F69-93B5-0CA124DF0A02@yahoo.com> <CABCOCHTrOkhfpvr2L9yRzXxVJjiF8pNYXQ-G8TLV8MD-i_XSpA@mail.gmail.com> <B04E9EA2-C43F-4DA4-9D93-DEFFEE20993D@yahoo.com> <SN6PR13MB2334E933702E18572EBCE6AF85999@SN6PR13MB2334.namprd13.prod.outlook.com>
In-Reply-To: <SN6PR13MB2334E933702E18572EBCE6AF85999@SN6PR13MB2334.namprd13.prod.outlook.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Tue, 02 Mar 2021 06:55:40 -0800
Message-ID: <CABCOCHSEjPuBpF0_g39yi7xUCd3YF-O-MWFQaCMYrQFOHmUAug@mail.gmail.com>
To: Linda Dunbar <linda.dunbar@futurewei.com>
Cc: Reshad Rahman <reshad=40yahoo.com@dmarc.ietf.org>, Roman Danyliw <rdd@cert.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>, JungSoo Park <pjs@etri.re.kr>, Yunchul Choi <cyc79@etri.re.kr>, YANG Doctors <yang-doctors@ietf.org>, Patrick Lingga <patricklink888@gmail.com>, skku-iotlab-members <skku-iotlab-members@googlegroups.com>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000003aa45b05bc8eeeab"
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/hhYkCkHQ76zkw5IKMe0GOB80kuQ>
Subject: Re: [yang-doctors] [I2nsf] Yangdoctors early review of draft-ietf-i2nsf-nsf-monitoring-data-model-04
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email list of the yang-doctors directorate <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2021 14:55:58 -0000
On Mon, Mar 1, 2021 at 4:21 PM Linda Dunbar <linda.dunbar@futurewei.com> wrote: > Andy and Reshad, > > > > Does it help if I request another YANG DR review? > Yes. I think the IESG should specify and document the procedures for follow-up YANG module reviews. We should avoid undocumented ad-hoc procedures that rely on email as the sole collaboration tool. IMO there should be a new review request for each updated revision. I especially want to know if the request is for an early review or WGLC review, and other contextual info. Andy > > Thanks, Linda > > > > *From:* I2nsf <i2nsf-bounces@ietf.org> *On Behalf Of * Reshad Rahman > *Sent:* Wednesday, February 24, 2021 10:40 AM > *To:* Andy Bierman <andy@yumaworks.com> > *Cc:* Roman Danyliw <rdd@cert.org>; i2nsf@ietf.org; JungSoo Park < > pjs@etri.re.kr>; Yunchul Choi <cyc79@etri.re.kr>; YANG Doctors < > yang-doctors@ietf.org>; Patrick Lingga <patricklink888@gmail.com>; > skku-iotlab-members <skku-iotlab-members@googlegroups.com>; Mr. Jaehoon > Paul Jeong <jaehoon.paul@gmail.com> > *Subject:* Re: [I2nsf] [yang-doctors] Yangdoctors early review of > draft-ietf-i2nsf-nsf-monitoring-data-model-04 > > > > > > > > *From: *Andy Bierman <andy@yumaworks.com> > *Date: *Wednesday, February 24, 2021 at 11:30 AM > *To: *Reshad Rahman <reshad@yahoo.com> > *Cc: *"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>, Roman Danyliw < > rdd@cert.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>, JungSoo Park < > pjs@etri.re.kr>, Yunchul Choi <cyc79@etri.re.kr>, Patrick Lingga < > patricklink888@gmail.com>, YANG Doctors <yang-doctors@ietf.org>, > skku-iotlab-members <skku-iotlab-members@googlegroups.com> > *Subject: *Re: [yang-doctors] [I2nsf] Yangdoctors early review of > draft-ietf-i2nsf-nsf-monitoring-data-model-04 > > > > > > > > On Mon, Feb 22, 2021 at 7:31 PM Reshad Rahman <reshad@yahoo.com> wrote: > > *I cannot figure out how to enter a new review in the IETF pages (even > logged in),* > > I have run into the same issue in the past. You need to go to the actual > review link, > https://datatracker.ietf.org/doc/draft-ietf-i2nsf-nsf-monitoring-data-model/reviewrequest/13767/ > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-nsf-monitoring-data-model%2Freviewrequest%2F13767%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C959faa31307f463f868c08d8dc7283ae%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637501731693750332%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qBtXhMguOMJEGkRkZ%2BBQsLffjtku4CV5x9kyyqiqa2U%3D&reserved=0> > in this case, and click on the “Correct review” button. My recollection is > that this will create a newer version of the review. > > > > > > But I am not modifying my review of the old draft. > > I am entering my review of the new draft. > > <RR> Version 00 will remain as a review of the old rev. The new version > will be a review of the new draft (you can provide a new reviewed revision). > > I agree that correct review implies that you can only change the review of > the old rev, so the button should probably be “Correct/new review” instead. > Anyway I believe that, even though the UI is misleading, you can enter a > new review while keeping the old review. > > > > Regards, > > Reshad. > > > > I think a better procedure would be for the authors to request a new > review for the updated draft. > > Hopefully the same reviewer can be assigned automatically. > > > > > > Regards, > > Reshad. > > > > > > Andy > > > > *From: *yang-doctors <yang-doctors-bounces@ietf.org> on behalf of Andy > Bierman <andy@yumaworks.com> > *Date: *Saturday, February 20, 2021 at 12:11 PM > *To: *"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> > *Cc: *Roman Danyliw <rdd@cert.org>, "i2nsf@ietf.org" <i2nsf@ietf.org>, > JungSoo Park <pjs@etri.re.kr>, Yunchul Choi <cyc79@etri.re.kr>, Patrick > Lingga <patricklink888@gmail.com>, YANG Doctors <yang-doctors@ietf.org>, > skku-iotlab-members <skku-iotlab-members@googlegroups.com> > *Subject: *Re: [yang-doctors] [I2nsf] Yangdoctors early review of > draft-ietf-i2nsf-nsf-monitoring-data-model-04 > > > > Hi, > > > > I have reviewed the module in draft-05. > > Thanks for the revision letter. That really helped make the review go fast. > > All my draft-04 comments have been addressed. > > > > I cannot figure out how to enter a new review in the IETF pages (even > logged in), > > so it is attached here. pyang is reporting some minor style issues. > > > > > > Status: Ready with nits (see attached file) > > > > > > Andy > > > > > > On Wed, Feb 17, 2021 at 7:15 AM Mr. Jaehoon Paul Jeong < > jaehoon.paul@gmail.com> wrote: > > Hi Andy, > > Patrick and I have addressed your comments on the following revision: > > > > > https://datatracker.ietf.org/doc/draft-ietf-i2nsf-nsf-monitoring-data-model/ > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-nsf-monitoring-data-model%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C959faa31307f463f868c08d8dc7283ae%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637501731693750332%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3gJHx%2F9sQfQbaiUYFQmxZidapOXeC53MUqVf6N1he%2Bw%3D&reserved=0> > > https://tools.ietf.org/html/draft-ietf-i2nsf-nsf-monitoring-data-model-05 > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-i2nsf-nsf-monitoring-data-model-05&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C959faa31307f463f868c08d8dc7283ae%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637501731693760323%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jEmAChZfGP2qMxfZScCg7I5jspjawUkF%2FtIMhG6DmXk%3D&reserved=0> > > > > I attach the revision letter to explain how to address your comments on > the revision. > > > > If you have further comments, please let me know. > > > > If you are satisfied with our revision, please update the YANG doctor > review status in the following link: > > > https://datatracker.ietf.org/doc/draft-ietf-i2nsf-nsf-monitoring-data-model/ > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-i2nsf-nsf-monitoring-data-model%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C959faa31307f463f868c08d8dc7283ae%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637501731693760323%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=dYm5Hu%2BAeYV1bBtcMZcACJjKYrtA96cmBAJoZqv2Ca0%3D&reserved=0> > > > > Thanks. > > > > Best Regards, > > Paul > > > > On Tue, Oct 6, 2020 at 3:03 AM Andy Bierman via Datatracker < > noreply@ietf.org> wrote: > > Reviewer: Andy Bierman > Review result: Almost Ready > > > > Major Issues: > > - None > > Moderate Issues: > > - top-level 'counters' container does not follow naming conventions. > Should start with 'i2nsf', probably 'i2nsf-state' > > - There do not seem to be any writable objects in the /counters > subtree so this container should have a 'config false' statement > > - top-level typedef and grouping description-stmts are self-referential > and not useful. Need to rewrite description-stmts and/or add > reference-stmts as needed. > > - grouping common-monitoring-data/time-stamp > Is this a different time stamp than the one in the NETCONF notification? > The 'message generation time' sounds like the standard timestamp. > Does this object represent the event detection time? > > - grouping i2nsf-system-alarm-type-content/usage > - grouping i2nsf-system-alarm-type-content/threshold > These are uint8 leafs with unclear descriptions. > Not sure why uint8 is the appropriate type. > Needs 1 or more of (reference, units, better description) > > - grouping traffic-rates > Add a units statement to each leaf. Not sure what units to use > but it should be consistent. (e.g, pps, bps used in descriptions > should also be in a units-stmt) > > - grouping i2nsf-system-counter-type-content > These counters should use the yang:counter32 type instead of uint32 > > - container counters/system-interface > - container counters/nsf-firewall > - container counters/nsf-policy-hits > The descriptions are too terse and confusing, and need a rewrite. > > - container counters/nsf-firewall > - container counters/nsf-policy-hits > - uses i2nsf-nsf-counters-type-content; > Many of the fields expanded from this grouping all say > they refer to 'the packet'. Why are they in this global > container of counters? E.g. (src-ip, dst-ip, src-port, dst-port) > Not clear at all how the server is supposed to apply this > grouping to these containers. > > - many leafs use "uint32" type for a rate. > Should add a units-stmt > > - leaf counters/nsf-policy-hits/hit-times > The purpose and type are confusing and generic. > If this is a counter then use counter32 > > - cut-and-paste for notification-stmt content should be replaced > with grouping/uses instead. Applies to the nsf-detection-* > and the various logging notifications. Even a grouping that > has 1 object in it is better than cut-and-paste 5+ times > > Minor Issues: > > - top-level identifiers are too generic > should have 'i2nsf-' prefix to be more reusable outside this module > > - quite a lot of identities that an implementation is required to support. > If this set of identities might change a lot faster than the > notifications and counter objects, then consider putting them > in a separate module > > - leaf with same type named differently; both intrusion-attack-type > - nsf-detection-intrusion/sub-attack-type > - nsf-log-intrusion/attack-type > > - quite a lot of notification event types for a server to implement > and a user to manage. All are mandatory (no if-feature statements). > Some such as nsf-detection-* subset are very similar. > A section or table would be useful that showed the YANG notification > names and their purpose -- maybe a reference to another RFC > with more details > > - there seems to be notifications for intrusion events and then > again for the logging of those events. This seems excessive > but > > > - grouping common-monitoring-data/time-stamp > Is this a different time stamp than the one in the NETCONF notification? > The 'message generation time' sounds like the standard timestamp. > Is this event detection time? > > - grouping common-monitoring-data/module-name > Is this a YANG module or some other type of module? > > - there is no way to configure which notifications should be generated > or maybe how often. YANG Push has its own dampening-period. > Since these are event stream subscriptions, not datastore subscriptions, > YANG-Push does not apply to this document at all. > > If there are a lot of notifications then a server implementation > might drop some > > - grouping i2nsf-nsf-event-type-content-extend/src-zone > - grouping i2nsf-nsf-event-type-content-extend/src-zone > These use type 'string'. Consider using a typedef that constrains > the string. General comment where unconstrained string is used: > The corner-case values such as empty string are often not allowed > in implementations. > > > - grouping i2nsf-nsf-event-type-content-extend/rule-id > - grouping i2nsf-nsf-event-type-content-extend/rule-name > - grouping i2nsf-nsf-event-type-content-extend/profile > These objects seem to reference objects in another YANG module. > If so, then leafref types might be more appropriate. > > - grouping i2nsf-nsf-event-type-content/rule-id > - grouping i2nsf-nsf-event-type-content/rule-name > - grouping i2nsf-nsf-event-type-content/profile > - grouping i2nsf-nsf-event-type-content/raw-info > These objects are cut-and-paste duplicates from > grouping i2nsf-nsf-event-type-content. They should > be in a separate grouping used by both. Also applies > to some other sets of objects > > - limits issues (e.g. current-session, maximum-session > The type is uint8. This is only OK it is impossible for any > implementation to ever have or want more than 255 of them. > If some other RFC really does limit the values where uint8 > is used, then that is OK. If so, a reference-stmt would help. > > > > _______________________________________________ > I2nsf mailing list > I2nsf@ietf.org > https://www.ietf.org/mailman/listinfo/i2nsf > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fi2nsf&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C959faa31307f463f868c08d8dc7283ae%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637501731693770318%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=btLcI1LT3ujHq73ICfGbJDyCKOP1teOZsuEL9dP7VDg%3D&reserved=0> > > > > _______________________________________________ yang-doctors mailing list > yang-doctors@ietf.org https://www.ietf.org/mailman/listinfo/yang-doctors > <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fyang-doctors&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C959faa31307f463f868c08d8dc7283ae%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637501731693770318%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2BFmmp8MqSGlZlpBgTBdbUyvpYiu1Ck3GGMxBgeJFuRA%3D&reserved=0> > >
- [yang-doctors] Yangdoctors early review of draft-… Andy Bierman via Datatracker
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Mr. Jaehoon Paul Jeong
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Andy Bierman
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Mr. Jaehoon Paul Jeong
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Andy Bierman
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Mr. Jaehoon Paul Jeong
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Andy Bierman
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Mr. Jaehoon Paul Jeong
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Andy Bierman
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Mr. Jaehoon Paul Jeong
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Mr. Jaehoon Paul Jeong
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Reshad Rahman
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Andy Bierman
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Reshad Rahman
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Linda Dunbar
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Andy Bierman
- Re: [yang-doctors] [I2nsf] Yangdoctors early revi… Linda Dunbar