Dear Glenn,
Thanks for your careful review and detailed comments/suggestions.
I have started to volunteer to help to move this document forward.
I posted a new revision and addressed all editorial things in that revision.
Please give me some more time for revising other parts,
in order to be
lenn's comments in
>> this revision.
> Thanks for addressing the comments. The MIB compiles OK and
> is looking good. It is shaping up well.
> A new set of comments is attached. Please check and do the
>
> needful.
> Glenn
> On 2017/02/21 16:50, Hiroshi Tsunoda wrote:
&g
Dear Glenn,
I posted a new revision MVPN-MIB document.
This revision addresses mainly editorial parts of your comments.
Although so many TBDs have remained, I hope that this becomes
the re-starting point to finalize this document.
URL:
https://www.ietf.org/id/draft-ietf-bess-mvpn-mib-03.txt
Hi Thomas,
Thank you very much for your answer. It is really helpful for me.
I am going to update the draft taking into account your answer.
Best regards,
-- tsuno
2017-08-11 16:50 GMT+02:00 Thomas Morin <thomas.mo...@orange.com>:
> Hi Tsuno,
>
> (below)
>
> Hiroshi Tsun
: Hiroshi Tsunoda
Duratation: 10 minutes
-- tsuno
2017-06-21 10:33 GMT+02:00 Martin Vigoureux <martin.vigour...@nokia.com>:
> All,
>
> it is time we start building the BESS WG agenda for Prague.
> The IETF agenda (still preliminary) is available at:
> https://datatracker.ietf.org/m
Hi,
Please forgive my insufficient knowledge about MVPN,
but I need some advice to answer the MIB doctor's
questions (attached in the end of this mail)
on L2L3-VPN-MCAST-{TC-MIB, MIB}.
a) Format and examples of Tunnel Identifier in PMSI Tunnel Attribute
L2L3-VPN-MCAST-TC-MIB provides a
On 2017/06/12 21:47, Glenn Mansfield Keeni wrote:
>>
>> Hi Tsuno,
>> Got this. I will be working on this. It is massive-
>> 40 pages. I hope to get back to you on this by the end
>> of next week.
>>
>> Cheers,
>>
>> Glenn
>> On 2017/
-vpn-mcast-mib-08
2017-05-02 14:44 GMT+02:00 Hiroshi Tsunoda <ts...@m.ieice.org>:
> 2017-05-01 12:32 GMT+02:00 Glenn Mansfield Keeni <gl...@cysols.com>:
>> Dear Tsuno/Zhang
>> Thanks for waiting. The review of
>> draft-ietf-bess-l2l3-vpn-mcast-mib-07 follow
Dear Glenn,
Thank you very much for your thorough review.
I have greatly appreciated it.
I am going to check and update the draft taking into
account your comments.
I try to submit the updated draft by the end of next week.
Best regards,
-- tsuno
2017-05-01 12:32 GMT+02:00 Glenn Mansfield
html/draft-ietf-bess-mvpn-mib-04
Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-bess-mvpn-mib-04
Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-mvpn-mib-04
Please see notes below for other changes.
2017-03-01 16:00 GMT+01:00 Hiroshi Tsunoda <ts...@m.ieice.org>:
Dear Glenn,
Thank you for your comments and for waiting for the update.
I posted a new revision (-10) as follows.
URL:
https://www.ietf.org/internet-drafts/draft-ietf-bess-l2l3-vpn-mcast-mib-10.txt
Htmlized:
https://tools.ietf.org/html/draft-ietf-bess-l2l3-vpn-mcast-mib-10
Dear Glenn,
May I ask you to give one more review
for draft-ietf-bess-l2l3-vpn-mcast-mib matter?
I posted a new revision (-12).
In this revision, I have made the following changes
in order to make the MIB simpler and be less
dependent on BGP.
- Added l2L3VpnMCastPmsiTunnelLeafInfoRequired
com>:
> Dear Tsuno,
> Thank you for the good work.
> All the issues are addressed. I have
> no further issues with this MIB. I
> believe the MIB review is complete.
>
> Thanks again for the cooperation during
> this long review period,.
>
> Glenn
>
>
&g
aming related mater-
> I would suggest
> s/l2L3VpnMcastPmsiFieldGroup/l2L3VpnMcastCoreGroup/
>
> Glenn
>
>
> On 2017/10/22 1:14, Hiroshi Tsunoda wrote:
>>
>> Dear Glenn,
>>
>> Thank you for your comments and for waiting for the update.
>>
Dear Glenn,
I have submitted the new version of BGP/MPLS Layer 3
VPN Multicast MIB.
(draft-ietf-bess-mvpn-mib-05.txt)
Since I have been focusing on draft-ietf-bess-l2-l3-vpn-mcast-mib matter,
this update includes only minor improvement. Sorry for the late progress.
I am going to simplify the MIB
:
https://datatracker.ietf.org/doc/html/draft-ietf-bess-l2l3-vpn-mcast-mib-13
Diff:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-l2l3-vpn-mcast-mib-13
Thanks in advance,
-- tsuno
2017-11-28 0:09 GMT+01:00 Hiroshi Tsunoda <ts...@m.ieice.org>:
> Dear Glenn,
>
> May I ask you t
pnMcastFullCompliance:
> MANDATORY-GROUPS {
>l2L3VpnMcastPmsiFieldGroup
>l2L3VpnMcastOptionalGroup
> }
>
>
> General:
> 10Page-2 Section-1
> 10.1In BGP/MPLS Virtual Private Networks (VPN)
> In BGP/MPLS
msiTunnelIfIndex OBJECT-TYPE
> REFERENCE
> "RFC2863 Sec. 3.1.5
>
>
>
>
> On 2018/05/02 6:59, Glenn Mansfield Keeni wrote:
>>
>> Hi Tsunoda,
>> Thanks for the good work.
>> I will start reviewing this right aw
; Implementors need to be aware that if the total number of
>> octets in MO1, MO2 and MO3 exceeds NNN, then OIDs of column
>> instances in this row will have more than 128 sub-identifiers
>> and cannot be accessed using SNMPv
Dear Glenn,
Thank you for waiting the update.
I have submitted the updated version of
draft-ietf-bess-mvpn-mib.
Links to the draft and diff are as follows.
URL:
https://www.ietf.org/internet-drafts/draft-ietf-bess-mvpn-mib-06.txt
Htmlized:
Hi Glenn,
I have submitted draft-ietf-bess-mvpn-mib-08.
Links to the draft and diff are as follows.
URL:
https://www.ietf.org/internet-drafts/draft-ietf-bess-mvpn-mib-08.txt
Htmlized: https://tools.ietf.org/html/draft-ietf-bess-mvpn-mib-08
Htmlized:
nk you for the
> good work. I have no further issues with the document
> and the MIB. I believe the MIB review is complete.
>
> Thanks again for your cooperation during this rather
> long and tedious review.
>
> Glenn
>
>
> On 2018/07/30 19:39, Hiroshi Tsunoda wrote:
>>
>
Hi Glenn,
I have submitted the updated version of draft-ietf-bess-mvpn-mib.
Links to the draft and diff are as follows.
URL:
https://www.ietf.org/internet-drafts/draft-ietf-bess-mvpn-mib-07.txt
Htmlized: https://tools.ietf.org/html/draft-ietf-bess-mvpn-mib-07
Htmlized:
Hi Benjamin,
Thank you very much for your thorough review and comments.
My replies are inline.
> Perhaps I'm confused, but "mvpnAdvtPeerAddr" appears in the security
> considerations in the list of address-related objects that may have
> privacy/security impact. That list is predicated on being
24 matches
Mail list logo
