1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
|
<pre>Internet Engineering Task Force (IETF) Y. Cui
Request for Comments: 7856 J. Dong
Category: Standards Track P. Wu
ISSN: 2070-1721 M. Xu
Tsinghua University
A. Yla-Jaaski
Aalto University
May 2016
<span class="h1">Softwire Mesh Management Information Base (MIB)</span>
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines objects for managing a softwire mesh.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7856">http://www.rfc-editor.org/info/rfc7856</a>.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Cui, et al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. The Internet-Standard Management Framework . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-3">3</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4">4</a>. Structure of the MIB Module . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4.1">4.1</a>. The swmSupportedTunnelTable Subtree . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4.2">4.2</a>. The swmEncapsTable Subtree . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4.3">4.3</a>. The swmBGPNeighborTable Subtree . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-4.4">4.4</a>. The swmConformance Subtree . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-5">5</a>. Relationship to Other MIB Modules . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-5.1">5.1</a>. Relationship to the IF-MIB . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-5.2">5.2</a>. Relationship to the IP Tunnel MIB . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-5.3">5.3</a>. MIB Modules Required for IMPORTS . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-6">6</a>. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-7">7</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-8">8</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-9">9</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-9.1">9.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-9.2">9.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The softwire mesh framework [<a href="./rfc5565" title=""Softwire Mesh Framework"">RFC5565</a>] is a tunneling mechanism that
enables connectivity between islands of IPv4 networks across a single
IPv6 backbone and vice versa. In a softwire mesh, extended
Multiprotocol BGP (MP-BGP) is used to set up tunnels and advertise
prefixes among Address Family Border Routers (AFBRs).
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines objects for managing a softwire mesh
[<a href="./rfc5565" title=""Softwire Mesh Framework"">RFC5565</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Internet-Standard Management Framework</span>
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to <a href="./rfc3410#section-7">section 7 of
RFC 3410</a> [<a href="./rfc3410" title=""Introduction and Applicability Statements for Internet- Standard Management Framework"">RFC3410</a>].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
<span class="grey">Cui, et al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
module that is compliant to the SMIv2, which is described in STD 58,
<a href="./rfc2578">RFC 2578</a> [<a href="./rfc2578" title=""Structure of Management Information Version 2 (SMIv2)"">RFC2578</a>], STD 58, <a href="./rfc2579">RFC 2579</a> [<a href="./rfc2579" title=""Textual Conventions for SMIv2"">RFC2579</a>] and STD 58, <a href="./rfc2580">RFC 2580</a>
[<a href="./rfc2580" title=""Conformance Statements for SMIv2"">RFC2580</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Terminology</span>
This document uses terminology from the softwire problem statement
[<a href="./rfc4925" title=""Softwire Problem Statement"">RFC4925</a>], the BGP encapsulation Subsequent Address Family Identifier
(SAFI), the BGP tunnel encapsulation attribute [<a href="./rfc5512" title=""The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute"">RFC5512</a>], the
softwire mesh framework [<a href="./rfc5565" title=""Softwire Mesh Framework"">RFC5565</a>], and the BGP IPsec tunnel
encapsulation attribute [<a href="./rfc5566" title=""BGP IPsec Tunnel Encapsulation Attribute"">RFC5566</a>].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in <a href="./rfc2119">RFC</a>
<a href="./rfc2119">2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Structure of the MIB Module</span>
The Softwire Mesh MIB provides a method to monitor the softwire mesh
objects through SNMP.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. The swmSupportedTunnelTable Subtree</span>
The swmSupportedTunnelTable subtree provides the information about
what types of tunnels can be used for softwire mesh scenarios in the
AFBR. The softwire mesh framework [<a href="./rfc5565" title=""Softwire Mesh Framework"">RFC5565</a>] does not mandate the use
of any particular tunneling technology. Based on the BGP tunnel
encapsulation attribute tunnel types introduced by <a href="./rfc5512">RFC 5512</a> [<a href="./rfc5512" title=""The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute"">RFC5512</a>]
and <a href="./rfc5566">RFC 5566</a> [<a href="./rfc5566" title=""BGP IPsec Tunnel Encapsulation Attribute"">RFC5566</a>], the softwire mesh tunnel types include at
least L2TPv3 (Layer 2 Tunneling Protocol version 3) over IP, GRE
(Generic Routing Encapsulation), Transmit tunnel endpoint, IPsec in
Tunnel-mode, IP in IP tunnel with IPsec Transport Mode, MPLS-in-IP
tunnel with IPsec Transport Mode, and IP in IP. The detailed
encapsulation information of different tunnel types (e.g., L2TPv3
Session ID, GRE Key, etc.) is not managed in the Softwire Mesh MIB.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. The swmEncapsTable Subtree</span>
The swmEncapsTable subtree provides softwire mesh NLRI-NH information
(Network Layer Reachability Information - Next Hop) about the AFBR.
It keeps the mapping between the External-IP (E-IP) prefix and the
Internal-IP (I-IP) address of the next hop. The mappings determine
which I-IP destination address will be used to encapsulate the
received packet according to its E-IP destination address. The
definitions of E-IP and I-IP are explained in <a href="./rfc5565#section-4.1">Section 4.1 of RFC 5565</a>
[<a href="./rfc5565" title=""Softwire Mesh Framework"">RFC5565</a>]. The number of entries in swmEncapsTable shows how many
softwire mesh tunnels are maintained in this AFBR.
<span class="grey">Cui, et al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. The swmBGPNeighborTable Subtree</span>
This subtree provides the softwire mesh BGP neighbor information of
an AFBR. It includes the address of the softwire mesh BGP peer and
the kind of tunnel that the AFBR would use to communicate with this
BGP peer.
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. The swmConformance Subtree</span>
This subtree provides the conformance information of MIB objects.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Relationship to Other MIB Modules</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Relationship to the IF-MIB</span>
The Interfaces MIB [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>] defines generic managed objects for
managing interfaces. Each logical interface (physical or virtual)
has an ifEntry. Tunnels are handled by creating logical interfaces
(ifEntry). Being a tunnel, the softwire mesh interface has an entry
in the Interface MIB, as well as an entry in the IP Tunnel MIB.
Those corresponding entries are indexed by ifIndex.
The ifOperStatus in the ifTable represents whether the mesh function
of the AFBR has been triggered. If the softwire mesh capability is
negotiated during the BGP OPEN phase, the mesh function is considered
to be started, and the ifOperStatus is "up". Otherwise, the
ifOperStatus is "down".
In the case of an IPv4-over-IPv6 softwire mesh tunnel, ifInUcastPkts
counts the number of IPv6 packets that are sent to the virtual
interface for decapsulation into IPv4. The ifOutUcastPkts counts the
number of IPv6 packets that are generated by encapsulating IPv4
packets sent to the virtual interface. In particular, if these IPv4
packets need fragmentation, ifOutUcastPkts counts the number of
packets after fragmentation.
In the case of an IPv6-over-IPv4 softwire mesh tunnel, ifInUcastPkts
counts the number of IPv4 packets that are delivered to the virtual
interface for decapsulation into IPv6. The ifOutUcastPkts counts the
number of IPv4 packets that are generated by encapsulating IPv6
packets sent down to the virtual interface. In particular, if these
IPv6 packets need to be fragmented, ifOutUcastPkts counts the number
of packets after fragmentation. Similar definitions apply to other
counter objects in the ifTable.
<span class="grey">Cui, et al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Relationship to the IP Tunnel MIB</span>
The IP Tunnel MIB [<a href="./rfc4087" title=""IP Tunnel MIB"">RFC4087</a>] contains objects applicable to all IP
tunnels, including softwire mesh tunnels. Meanwhile, the Softwire
Mesh MIB extends the IP Tunnel MIB to further describe encapsulation-
specific information.
When running a point-to-multipoint tunnel, it is necessary for a
softwire mesh AFBR to maintain an encapsulation table in order to
perform correct "forwarding" among AFBRs. This forwarding function
on an AFBR is performed by using the E-IP destination address to look
up the I-IP encapsulation destination address in the encapsulation
table. An AFBR also needs to know the BGP peer information of the
other AFBRs, so that it can negotiate the NLRI-NH information and the
tunnel parameters with them.
The Softwire Mesh MIB requires the implementation of the IP Tunnel
MIB. The tunnelIfEncapsMethod in the tunnelIfEntry MUST be set to
softwireMesh(16), and a corresponding entry in the Softwire Mesh MIB
module will be presented for the tunnelIfEntry. The
tunnelIfRemoteInetAddress MUST be set to "0.0.0.0" for IPv4 or "::"
for IPv6 because it is a point-to-multipoint tunnel.
The tunnelIfAddressType in the tunnelIfTable represents the type of
address in the corresponding tunnelIfLocalInetAddress and
tunnelIfRemoteInetAddress objects. The tunnelIfAddressType is
identical to swmEncapsIIPDstType in softwire mesh, which can support
either IPv4-over-IPv6 or IPv6-over-IPv4. When the
swmEncapsEIPDstType is IPv6 and the swmEncapsIIPDstType is IPv4, the
tunnel type is IPv6-over-IPv4; when the swmEncapsEIPDstType is IPv4
and the swmEncapsIIPDstType is IPv6, the encapsulation mode is IPv4-
over-IPv6.
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. MIB Modules Required for IMPORTS</span>
The following MIB module IMPORTS objects from SNMPv2-SMI [<a href="./rfc2578" title=""Structure of Management Information Version 2 (SMIv2)"">RFC2578</a>],
SNMPv2-CONF [<a href="./rfc2580" title=""Conformance Statements for SMIv2"">RFC2580</a>], IF-MIB [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>], and INET-ADDRESS-MIB
[<a href="./rfc4001" title=""Textual Conventions for Internet Network Addresses"">RFC4001</a>].
<span class="grey">Cui, et al. Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Definitions</span>
SOFTWIRE-MESH-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2 FROM SNMPv2-SMI
OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF
InetAddress, InetAddressType, InetAddressPrefixLength
FROM INET-ADDRESS-MIB
ifIndex FROM IF-MIB
IANAtunnelType FROM IANAifType-MIB;
swmMIB MODULE-IDENTITY
LAST-UPDATED "201605110000Z" -- May 11, 2016
ORGANIZATION "Softwire Working Group"
CONTACT-INFO
"Yong Cui
Email: yong@csnet1.cs.tsinghua.edu.cn
Jiang Dong
Email: knight.dongjiang@gmail.com
Peng Wu
Email: weapon9@gmail.com
Mingwei Xu
Email: xmw@cernet.edu.cn
Antti Yla-Jaaski
Email: antti.yla-jaaski@aalto.fi
Email comments directly to the Softwire WG Mailing
List at softwires@ietf.org
"
DESCRIPTION
"This MIB module contains managed object definitions for
the softwire mesh framework.
Copyright (c) 2016 IETF Trust and the persons
identified as authors of the code. All rights reserved.
Redistribution and use in source and binary forms, with
or without modification, is permitted pursuant to, and
<span class="grey">Cui, et al. Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
subject to the license terms contained in, the Simplified
BSD License set forth in <a href="#section-4">Section 4</a>.c of the IETF Trust's
Legal Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>)."
REVISION "201605110000Z"
DESCRIPTION "Initial version, published as <a href="./rfc7856">RFC 7856</a>"
::= { mib-2 239 }
swmObjects OBJECT IDENTIFIER ::= { swmMIB 1 }
-- swmSupportedTunnelTable
swmSupportedTunnelTable OBJECT-TYPE
SYNTAX SEQUENCE OF SwmSupportedTunnelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that show what kinds of tunnels
can be supported by the AFBR."
::= { swmObjects 1 }
swmSupportedTunnelEntry OBJECT-TYPE
SYNTAX SwmSupportedTunnelEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that show what kinds of tunnels
can be supported in the AFBR. If the AFBR supports
multiple tunnel types, the swmSupportedTunnelTable
would have several entries."
INDEX { swmSupportedTunnelType }
::= { swmSupportedTunnelTable 1 }
SwmSupportedTunnelEntry ::= SEQUENCE {
swmSupportedTunnelType IANAtunnelType
}
swmSupportedTunnelType OBJECT-TYPE
SYNTAX IANAtunnelType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the tunnel type that can be used for softwire
mesh scenarios, such as L2TPv3 over IP, GRE, Transmit
tunnel endpoint, IPsec in Tunnel-mode, IP in IP tunnel with
IPsec Transport Mode, MPLS-in-IP tunnel with IPsec Transport
Mode, and IP in IP. There is no restriction on the tunnel
type the softwire mesh can use."
REFERENCE
<span class="grey">Cui, et al. Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
"L2TPv3 over IP, GRE, and IP in IP in <a href="./rfc5512">RFC 5512</a>.
Transmit tunnel endpoint, IPsec in Tunnel-mode, IP in IP
tunnel with IPsec Transport Mode, MPLS-in-IP tunnel with
IPsec Transport Mode in <a href="./rfc5566">RFC 5566</a>."
::= { swmSupportedTunnelEntry 1 }
-- end of swmSupportedTunnelTable
--swmEncapsTable
swmEncapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SwmEncapsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display the
softwire mesh encapsulation information."
::= { swmObjects 2 }
swmEncapsEntry OBJECT-TYPE
SYNTAX SwmEncapsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that manage the softwire mesh I-IP
encapsulation destination based on the E-IP destination
prefix."
INDEX { ifIndex,
swmEncapsEIPDstType,
swmEncapsEIPDst,
swmEncapsEIPPrefixLength
}
::= { swmEncapsTable 1 }
SwmEncapsEntry ::= SEQUENCE {
swmEncapsEIPDstType InetAddressType,
swmEncapsEIPDst InetAddress,
swmEncapsEIPPrefixLength InetAddressPrefixLength,
swmEncapsIIPDstType InetAddressType,
swmEncapsIIPDst InetAddress
}
swmEncapsEIPDstType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the address type used for
swmEncapsEIPDst. It is different from the
<span class="grey">Cui, et al. Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
tunnelIfAddressType in the tunnelIfTable. The
swmEncapsEIPDstType is IPv6 (2) if it is IPv6-over-IPv4
tunneling. The swmEncapsEIPDstType is
IPv4 (1) if it is IPv4-over-IPv6 tunneling."
REFERENCE
"IPv4 and IPv6 in <a href="./rfc4001">RFC 4001</a>."
::= { swmEncapsEntry 1 }
swmEncapsEIPDst OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The E-IP destination prefix, which is
used for I-IP encapsulation destination looking up.
The type of this address is determined by the
value of swmEncapsEIPDstType"
REFERENCE
"E-IP and I-IP in <a href="./rfc5565">RFC 5565</a>."
::= { swmEncapsEntry 2 }
swmEncapsEIPPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The prefix length of the E-IP destination prefix."
::= { swmEncapsEntry 3 }
swmEncapsIIPDstType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the address type used for
swmEncapsIIPDst. It is the same as the tunnelIfAddressType
in the tunnelIfTable."
REFERENCE
"IPv4 and IPv6 in <a href="./rfc4001">RFC 4001</a>."
::= { swmEncapsEntry 4 }
swmEncapsIIPDst OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The I-IP destination address, which is used as the
encapsulation destination for the corresponding E-IP
<span class="grey">Cui, et al. Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
prefix. Since the tunnelIfRemoteInetAddress in the
tunnelIfTable should be 0.0.0.0 or ::, swmEncapIIPDst
should be the destination address used in the outer
IP header."
REFERENCE
"E-IP and I-IP in <a href="./rfc5565">RFC 5565</a>."
::= { swmEncapsEntry 5 }
-- End of swmEncapsTable
-- swmBGPNeighborTable
swmBGPNeighborTable OBJECT-TYPE
SYNTAX SEQUENCE OF SwmBGPNeighborEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table of objects that display the softwire mesh
BGP neighbor information."
::= { swmObjects 3 }
swmBGPNeighborEntry OBJECT-TYPE
SYNTAX SwmBGPNeighborEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A set of objects that display the softwire mesh
BGP neighbor information."
INDEX {
ifIndex,
swmBGPNeighborInetAddressType,
swmBGPNeighborInetAddress
}
::= { swmBGPNeighborTable 1 }
SwmBGPNeighborEntry ::= SEQUENCE {
swmBGPNeighborInetAddressType InetAddressType,
swmBGPNeighborInetAddress InetAddress,
swmBGPNeighborTunnelType IANAtunnelType
}
swmBGPNeighborInetAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object specifies the address type used for
swmBGPNeighborInetAddress."
::= { swmBGPNeighborEntry 1 }
<span class="grey">Cui, et al. Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
swmBGPNeighborInetAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address of the AFBR's BGP neighbor. The
address type is the same as the tunnelIfAddressType
in the tunnelIfTable."
::= { swmBGPNeighborEntry 2 }
swmBGPNeighborTunnelType OBJECT-TYPE
SYNTAX IANAtunnelType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Represents the type of tunnel that the AFBR
chooses to transmit traffic with another AFBR/BGP
neighbor."
::= { swmBGPNeighborEntry 3 }
-- End of swmBGPNeighborTable
-- conformance information
swmConformance
OBJECT IDENTIFIER ::= { swmMIB 2 }
swmCompliances
OBJECT IDENTIFIER ::= { swmConformance 1 }
swmGroups
OBJECT IDENTIFIER ::= { swmConformance 2 }
-- compliance statements
swmCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Describes the requirements for conformance to the Softwire
Mesh MIB.
The following index objects cannot be added as OBJECT
clauses but nevertheless have compliance requirements:
"
-- OBJECT swmEncapsEIPDstType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
-- OBJECT swmEncapsEIPDst
<span class="grey">Cui, et al. Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
-- SYNTAX InetAddress (SIZE(4|16))
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
-- OBJECT swmEncapsEIPPrefixLength
-- SYNTAX InetAddressPrefixLength (Unsigned32 (0..128))
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
-- OBJECT swmBGPNeighborInetAddressType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
-- OBJECT swmBGPNeighborInetAddress
-- SYNTAX InetAddress (SIZE(4|16))
-- DESCRIPTION
-- "An implementation is required to support
-- global IPv4 and/or IPv6 addresses, depending
-- on its support for IPv4 and IPv6."
MODULE -- this module
MANDATORY-GROUPS {
swmSupportedTunnelGroup,
swmEncapsGroup,
swmBGPNeighborGroup
}
::= { swmCompliances 1 }
swmSupportedTunnelGroup OBJECT-GROUP
OBJECTS {
swmSupportedTunnelType
}
STATUS current
DESCRIPTION
"The collection of objects that are used to show
what kind of tunnel the AFBR supports."
::= { swmGroups 1 }
swmEncapsGroup OBJECT-GROUP
OBJECTS {
swmEncapsIIPDst,
<span class="grey">Cui, et al. Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
swmEncapsIIPDstType
}
STATUS current
DESCRIPTION
"The collection of objects that are used to display
softwire mesh encapsulation information."
::= { swmGroups 2 }
swmBGPNeighborGroup OBJECT-GROUP
OBJECTS {
swmBGPNeighborTunnelType
}
STATUS current
DESCRIPTION
"The collection of objects that are used to display
softwire mesh BGP neighbor information."
::= { swmGroups 3 }
END
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
Because this MIB module reuses the IP Tunnel MIB, the security
considerations of the IP Tunnel MIB are also applicable to the
Softwire Mesh MIB.
There are no management objects defined in this MIB module that have
a MAX-ACCESS clause of read-write and/or read-create. So, if this
MIB module is implemented correctly, then there is no risk that an
intruder can alter or create any management objects of this MIB
module via direct SNMP SET operations.
Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the objects and their sensitivity/
vulnerability:
swmSupportedTunnelType, swmEncapsIIPDstType, swmEncapsIIPDst, and
swmBGPNeighborTunnelType can expose the types of tunnels used within
the internal network and potentially reveal the topology of the
internal network.
<span class="grey">Cui, et al. Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec),
there is no control as to who on the secure network is allowed to
access and GET/SET (read/change/create/delete) the objects in this
MIB module.
Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [<a href="./rfc3410" title=""Introduction and Applicability Statements for Internet- Standard Management Framework"">RFC3410</a>]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM)
[<a href="./rfc3414" title=""User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)"">RFC3414</a>] with the AES cipher algorithm [<a href="./rfc3826" title=""The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model"">RFC3826</a>]. Implementations
MAY also provide support for the Transport Security Model (TSM)
[<a href="./rfc5591" title=""Transport Security Model for the Simple Network Management Protocol (SNMP)"">RFC5591</a>] in combination with a secure transport such as SSH
[<a href="./rfc5592" title=""Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)"">RFC5592</a>] or TLS/DTLS [<a href="./rfc6353" title=""Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)"">RFC6353</a>].
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
IANA has allocated the following OBJECT IDENTIFIER value and recorded
it in the SMI Numbers registry in the subregistry called "SMI Network
Management MGMT Codes Internet-standard MIB" under the mib-2 branch
(1.3.6.1.2.1):
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
swmMIB { mib-2 239 }
IANA has recorded the following IANAtunnelType Textual Convention
within the IANAifType-MIB:
IANAtunnelType ::= TEXTUAL-CONVENTION
SYNTAX INTEGER {
softwireMesh(16) -- softwire mesh tunnel
}
<span class="grey">Cui, et al. Standards Track [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
DOI 10.17487/RFC2119, March 1997,
<<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>>.
[<a id="ref-RFC2578">RFC2578</a>] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, <a href="./rfc2578">RFC 2578</a>,
DOI 10.17487/RFC2578, April 1999,
<<a href="http://www.rfc-editor.org/info/rfc2578">http://www.rfc-editor.org/info/rfc2578</a>>.
[<a id="ref-RFC2579">RFC2579</a>] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, <a href="./rfc2579">RFC 2579</a>, DOI 10.17487/RFC2579, April 1999,
<<a href="http://www.rfc-editor.org/info/rfc2579">http://www.rfc-editor.org/info/rfc2579</a>>.
[<a id="ref-RFC2580">RFC2580</a>] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Conformance Statements for SMIv2",
STD 58, <a href="./rfc2580">RFC 2580</a>, DOI 10.17487/RFC2580, April 1999,
<<a href="http://www.rfc-editor.org/info/rfc2580">http://www.rfc-editor.org/info/rfc2580</a>>.
[<a id="ref-RFC3414">RFC3414</a>] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, <a href="./rfc3414">RFC 3414</a>,
DOI 10.17487/RFC3414, December 2002,
<<a href="http://www.rfc-editor.org/info/rfc3414">http://www.rfc-editor.org/info/rfc3414</a>>.
[<a id="ref-RFC3826">RFC3826</a>] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", <a href="./rfc3826">RFC 3826</a>,
DOI 10.17487/RFC3826, June 2004,
<<a href="http://www.rfc-editor.org/info/rfc3826">http://www.rfc-editor.org/info/rfc3826</a>>.
[<a id="ref-RFC4001">RFC4001</a>] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", <a href="./rfc4001">RFC 4001</a>, DOI 10.17487/RFC4001, February 2005,
<<a href="http://www.rfc-editor.org/info/rfc4001">http://www.rfc-editor.org/info/rfc4001</a>>.
[<a id="ref-RFC5512">RFC5512</a>] Mohapatra, P. and E. Rosen, "The BGP Encapsulation
Subsequent Address Family Identifier (SAFI) and the BGP
Tunnel Encapsulation Attribute", <a href="./rfc5512">RFC 5512</a>,
DOI 10.17487/RFC5512, April 2009,
<<a href="http://www.rfc-editor.org/info/rfc5512">http://www.rfc-editor.org/info/rfc5512</a>>.
<span class="grey">Cui, et al. Standards Track [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
[<a id="ref-RFC5565">RFC5565</a>] Wu, J., Cui, Y., Metz, C., and E. Rosen, "Softwire Mesh
Framework", <a href="./rfc5565">RFC 5565</a>, DOI 10.17487/RFC5565, June 2009,
<<a href="http://www.rfc-editor.org/info/rfc5565">http://www.rfc-editor.org/info/rfc5565</a>>.
[<a id="ref-RFC5566">RFC5566</a>] Berger, L., White, R., and E. Rosen, "BGP IPsec Tunnel
Encapsulation Attribute", <a href="./rfc5566">RFC 5566</a>, DOI 10.17487/RFC5566,
June 2009, <<a href="http://www.rfc-editor.org/info/rfc5566">http://www.rfc-editor.org/info/rfc5566</a>>.
[<a id="ref-RFC5591">RFC5591</a>] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)",
STD 78, <a href="./rfc5591">RFC 5591</a>, DOI 10.17487/RFC5591, June 2009,
<<a href="http://www.rfc-editor.org/info/rfc5591">http://www.rfc-editor.org/info/rfc5591</a>>.
[<a id="ref-RFC5592">RFC5592</a>] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management
Protocol (SNMP)", <a href="./rfc5592">RFC 5592</a>, DOI 10.17487/RFC5592, June
2009, <<a href="http://www.rfc-editor.org/info/rfc5592">http://www.rfc-editor.org/info/rfc5592</a>>.
[<a id="ref-RFC6353">RFC6353</a>] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)",
STD 78, <a href="./rfc6353">RFC 6353</a>, DOI 10.17487/RFC6353, July 2011,
<<a href="http://www.rfc-editor.org/info/rfc6353">http://www.rfc-editor.org/info/rfc6353</a>>.
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
[<a id="ref-RFC2863">RFC2863</a>] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", <a href="./rfc2863">RFC 2863</a>, DOI 10.17487/RFC2863, June 2000,
<<a href="http://www.rfc-editor.org/info/rfc2863">http://www.rfc-editor.org/info/rfc2863</a>>.
[<a id="ref-RFC3410">RFC3410</a>] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", <a href="./rfc3410">RFC 3410</a>,
DOI 10.17487/RFC3410, December 2002,
<<a href="http://www.rfc-editor.org/info/rfc3410">http://www.rfc-editor.org/info/rfc3410</a>>.
[<a id="ref-RFC4087">RFC4087</a>] Thaler, D., "IP Tunnel MIB", <a href="./rfc4087">RFC 4087</a>,
DOI 10.17487/RFC4087, June 2005,
<<a href="http://www.rfc-editor.org/info/rfc4087">http://www.rfc-editor.org/info/rfc4087</a>>.
[<a id="ref-RFC4925">RFC4925</a>] Li, X., Ed., Dawkins, S., Ed., Ward, D., Ed., and A.
Durand, Ed., "Softwire Problem Statement", <a href="./rfc4925">RFC 4925</a>,
DOI 10.17487/RFC4925, July 2007,
<<a href="http://www.rfc-editor.org/info/rfc4925">http://www.rfc-editor.org/info/rfc4925</a>>.
<span class="grey">Cui, et al. Standards Track [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
Acknowledgements
The authors would like to thank Dave Thaler, Jean-Philippe Dionne, Qi
Sun, Sheng Jiang, and Yu Fu for their valuable comments.
Authors' Addresses
Yong Cui
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
China
Phone: +86-10-6260-3059
Email: yong@csnet1.cs.tsinghua.edu.cn
Jiang Dong
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
China
Phone: +86-10-6278-5822
Email: knight.dongjiang@gmail.com
Peng Wu
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
China
Phone: +86-10-6278-5822
Email: weapon9@gmail.com
Mingwei Xu
Tsinghua University
Department of Computer Science, Tsinghua University
Beijing 100084
China
Phone: +86-10-6278-5822
Email: xmw@cernet.edu.cn
<span class="grey">Cui, et al. Standards Track [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc7856">RFC 7856</a> Softwire Mesh MIB May 2016</span>
Antti Yla-Jaaski
Aalto University
Konemiehentie 2
Espoo 02150
Finland
Phone: +358-40-5954222
Email: antti.yla-jaaski@aalto.fi
Cui, et al. Standards Track [Page 18]
</pre>
|
