NVRAM에 저장되어 있는 Configuration register 값은 각각의 의미를 지닌 16bit로 구성되어 있고 16진수로 표현 된다. 예를 들어 router의 default configuration register값인 0x2102 를 이진수로 변환하면 다음과 같은 값들이 표현된다.

예를 들어 위 그림의 표에서 6번 bit가 ‘1’로 설정되면 부팅 시 NVRAM을 참조 하지 말라는 의미로 사용된다. 즉 부팅 시에 Configuration 정보를 참조하지 말고 초기 상태로 부팅하라는 의미이다. 이 값은 password recovery를 수
행하는 경우에 변경되는 값이기도 한다. 이 중에 부팅 시에 가장 중요하게 참조되는 부분은 바로 boot field이다.
boot field에서 표현하는 정보는 IOS Image의 참조 위치를 알려주는 정보이 며 다음과 같은 정보를 제공하고 있다.

Boot Field Meaning
------------------------------------------------------------------------------------
0x0 (0000) Stays at the system bootstrap prompt
0x1 (0001) Boots system image on EPROM
0x2-F (0010 ~ ) Specifies a default netboot filename Enables boot
system commands that override default netboot filename

Boot field의 Default값은 0x2(0010)이다. 이는 IOS Device가 부팅 시에 기본적으로 flash memory에서 IOS Image를 참조한다는 의미이다.

출처 - 네트워크 전문가 따라잡기( http://cafe.naver.com/neteg.cafe )

◎ 모뎀상태를 확인할 수 있는 indicator
: * : power-level이 3dB 이상 변화 발생
: ! : cable modem이 상향신호를 최대로 출력 중

◎ show interfaces cable 2/0(3/0) upstream 0(0~5)
ⓐ interface or upstream port별 TX, RX 속도 확인

ⓑ 확인 결과 70 ~ 80 ~ 90%가 지속되면 Cell 분할 및 가입자수를 각 상향 Port별 균등하게 분할 필요

◎ show controllers cable 2/0(3/0) upstream 0(0~5)

ⓐ 상향 Port의 신호레벨 (SNR) 확인

ⓑ 25dB이상이어야 정상이며, 30dB 이상 나오면 최적이고, 20dB 까지 모뎀 online 가능

ⓒ 상향변조방식 QPSK (25dB이상), 16QAM(30dB이상)

ⓓ SNR이 적을 경우
: 상향 신호세기 자체가 낮을 경우 : 증폭기의 상향 증폭레벨 조정
: 잡음이 많을 경우 : 케이블망 상향선로 정비로 유입잡음 차단 및 Tap Off단에 filter 장착 (20MHz 이하 차단)

◎모뎀 online 후 PC가 IP Address를 받지 못하면 CM에 연결된 PC수를 확인 후 모뎀이 잡고 있는 PC NIC MAC Address를 clear 시켜줌

ⓐ sh cable modem x.x.x.x detail 명령어로 max-cpe 개수 확인
: x.x.x.x ( IP / MAC Address )

ⓑ sh int c2/0(3/0) modem sid # 명령어로 모뎀에 연결되어 있는 MAC Address 확인
: sh cable modem x.x.x.x 결과 에서 Prim Sid 번호가 　#　임

ⓒ 정상적인 IP/MAC이 있더라도 Internet을 사용하지 못하면 clear cable host x.x.x.x 로 해당 MAC 제거
: clear cable host x.x.x.x

예제 청원유선만해당

월곡 탑연 show cable modem | inc Cable2/0/U0

오송1,2,3,4 동평 보영@ show cable modem | inc Cable2/0/U1

월탄 교원대근처 show cable modem | inc Cable2/0/U2

중봉(봉산,정중,서평) show cable modem | inc Cable2/0/U3

궁평1.2구 show cable modem | inc Cable2/0/U4

대평유선 show cable modem | inc Cable2/0/U5

online 된 모뎀만 볼 수 있음 show cable modem | inc online

각 포트별 전체 모뎀 show cable modem summary total

show cable modem detail 각모뎀별 내용을 볼 수 있음

sh int c2/0 up | inc util CMTS 상향 Port의 Utilization 값 확인

sh int c2/0 modem 000 (sid) lancard mac 확인

utilization이 70~90%이상 계속해서 사용될 경우 해당 Port에 연결된 CM뒤의 가입자들은 상향쪽으로
Bottleneck이 발생하여 결과적으로 속도가 저하됨

sh cable flap-list c2/0 up 0

cable flap-list 확인하여 해당모뎀의 최근 flap이 언제 발생했는지 확인 및
상향쪽 miss가 hit에 비해 많거나, CRC가 발생한다면 상향 Route 확인 지시

show interfaces cable 2/0 upstream 0 port별 TX, RX 속도 확인

# show cable modem : 모뎀의 전체적인 상황 볼 수 있다.
# show cable modem | inc online : online 된 모뎀만 볼 수 있음
# show cable modem | inc offline : offline 된 모뎀만 볼 수 있음
# show cable modem | inc init : init 상태의 모뎀 볼 수 있음
# show cable modem summary total : 각 포트별 전체 모뎀의 상태 볼 수 있음
# show cable modem | inc MAC Address 또는 10.x.x.x : 특정 모뎀만 선택해서 볼 수 있음
# show cable modem | inc Cable2/0/U0 : 2번 Card의 0 번 포트의 모뎀만 볼 수 있음
(마지막 숫자에 따라서 포트 구별 됨)
# show interface 2/0 modem sid 값 : show cable modem 에서 나타난 sid 값으로 모뎀의 상태와 모뎀에 연결된 PC의 IP 를 볼 수 있음
# clear cable modem IP 나 MAC Address reset : 특정 모뎀을 reset 시킬 수 있음
clear cable modem MAC reset
# clear cable host IP 나 MAC Address : 모뎀에 연결된 PC 가 가지고간 IP 삭제
# clear cable modem all reset : 모든 모뎀을 reset 시킬 수 있음(주의해서 사용)
# show controllers Cable2/0 | inc SNR : 각 상향 포트별의 SNR 값 볼 수 있음
# show cable hop : 각 포트별 상향 주파수 확인
상향 포트 주파수 변환 방법
(상향 설정된 주파수 대역에 잡음이 많거나 SNR 값이 나쁠 때 사용)
i) # show cable hop로 상향 주파ii) 수 확인
iii) # test cable hop cable2/0 upstream 0(포트번호)
iv) # show cable hop로 상향 변경 주파v) 수 확인
vi) ii) 항목 한번 사용시 한 단계씩 변함(세번 입력하면 원래 값으로 돌아옴)

명령어 추가

show env all :cmts 건강상태보기

clear cab modem 00a0.736a.4475 reset 특정모뎀리셋
sh cab hop 포트별주파수 확인
test cab hop c2/0 up5 5번상향포트의 주파수변경
sh cab modem 0000.0000.0000 특정모뎀의 rx레벨확인 및 상태 보기
sh cab modem detail 모뎀별 신호 잡음비
sh cab modem detail | inc 444 특정모뎀의 신호잡음비
clear cab host [ip or mac] 랜카드가 받아간 아이피 리셋
sh int c2/0 modem 0 전체호스트의 ip 확인
sh int c2/0 modem 0 | inc 317 특정호스트의 ip확인
sh cab f hit/miss p-adj(3dB조정명령)
sh cab f sort-f cab f를 p-adj 많은순으로 정렬
sh cab f sort-t cab f를 시간으로 정렬
sh cab f c3/0 up1 sort-f 특정포트의 cab f p-adj순 정렬
sh cab f c3/0 up1 | inc 0000.0000.0000 특정모뎀의 cab f 보기
clear cable flap-list all flap-list 초기화
clear cable flap-list 0000.0000.0000 특정모뎀의 cab f 최기화
sh cab modem su cmts의 전체 모뎀수
sh int c2/0 sid counter 가입자별 상향트래픽
sh int c2/0 u1 포트별트래픽
sh contr c2/0 u1 포트별신호잡음비
sh cab modem c2/0 up 1 : inc ! 특정포트의 !만 색출(!는 모뎀이 상향을MAX보냄)
configure terminal config 모드로 전환

◎ 속도가 느려요
가) CMTS 상향 Port의 SNR 확인 및 cable flap-list 확인

ⓐ 모뎀이 붙어있는 상향 Port의 SNR비 확인, 아주(20 ~ 25dB 이하) 낮아졌다면 상향 조정지시
: 잡음 때문에 SNR 값이 떨어진 것인지, 상향 신호세기가 일정하지 못한지 방송사에서 확인
: cmts#sh contr c3/0 up | inc SNR (엔터)
SNR 28.6280 dB
SNR 19.840 dB
SNR 26.200 dB
SNR 25.5760 dB
SNR 28.9440 dB
SNR 27.6040 dB (위 부터 C3/0의 0~5번 Port를 말함)

ⓑ cable flap-list 확인하여 해당모뎀의 최근 flap이 언제 발생했는지 확인 및
상향쪽 miss가 hit에 비해 많거나, CRC가 발생한다면 상향 Route 확인 지시
: cmts#sh cable flap-list c3/0 up 0 (엔터)
MAC Address Upstream Ins Hit Miss CRC P-Adj Flap Time
0000.f031.8689 Cable3/0/U0 19 43799 25131 20 721 1358 Feb 20 16:06:01
0090.9601.65be Cable3/0/U0 65 9575 2051 1 !936 1126 Feb 20 14:15:08
00a0.736a.9144 Cable3/0/U0 3 64431 638 2 813 841 Feb 19 17:01:49
0090.9601.3da8 Cable3/0/U0 140 20745 3528 2 3 381 Feb 20 17:29:32
0000.f028.7e93 Cable3/0/U0 65 19184 10474 1 51 349 Feb 20 20:12:44
0090.9601.7285 Cable3/0/U0 77 9756 2668 0 0 260 Feb 20 18:06:07

ⓒ APT가입자중 PC IP Address를 확인하여 CMTS에 할당한 IP 및 해당 Router가 일치하지
않으면 해당 Switching Hub에 연결된 가입자중에 하나가 IP 공유 Program을 사용하고 있어
가입자에게 다른 IP를 할당하게 되어 통신이 불가하거나, 통신이 되어도 속도가 느려지게 됨

나) CMTS 상향 Port의 Utilization 값 확인 및 상향 과다 사용 시 상향 대역폭 확장

ⓐ sh int c2/0(3/0) up | inc util (엔터)
: cmts#sh int c3/0 up | inc util
Avg upstream channel utilization : 9%
Avg upstream channel utilization : 25%
Avg upstream channel utilization : 74%
Avg upstream channel utilization : 21%
Avg upstream channel utilization : 92%
Avg upstream channel utilization : 15% (위 부터 C3/0의 0~5번 Port를 말함)
: utilization이 70~90%이상 계속해서 사용될 경우 해당 Port에 연결된 CM뒤의 가입자들은 상향쪽으로
Bottleneck이 발생하여 결과적으로 속도가 저하됨

ⓑ 상향 Port별 SNR 값 30dB 이상, 잡음/SNR값 변동 없고 42MHz까지 지원 가능한 Port에 한해 대역폭 확장

다) 상향 과다 사용자 색출 및 상향속도 제한

ⓐ sh int c2/0(3/0) sic counters (엔터)
: 시간차를 두고 명령어를 2회 실시한 후 그 결과를 근거로 상향사용자 추적
: 　inoctets　를 기준으로 sorting 하여 증가가 가장 많이된 sid번호가 상향 과다 사용자

ⓑ 상향과다 사용자를 대상으로 CNR에서 상향을 제한하는 Client-Class, Policy를 생성 : 데이콤 신청
: 모뎀 등록 변경
: 모뎀 원격 Reset : 반드시 reset를 걸어줘야 함

ⓒ 위 방법은 단시간 내에 확인하는 방법이기 때문에 상향과다 사용자를 정확히 색출하기 어려움
따라서 주기적으로 적어도 2~3일 정도 차이를 두고 　inoctets　값을 비교해서 추적하는 것이 타당함

ⓓ 위 방법은 단기적인 방법이므로 적절한 Cell 분할로 상향 Port별 가입자를 균등하게 분배하는 것과
상향 망 개선 후 변조방식 및 상향 대역폭을 변경하는 방법이 있음

* ping 안될시 ping docsis [ip주소] 로 확인가능. - ping doc [ip번호]

▣ DOCSIS 1.0 / 1.1 명령어----------------------------------------
◎ (1.0) Max CPE / SNR 확인 (scm d | inc [mac-add뒷자리])
show cable modem detail | include [mac-add]

◎ (1.1) Max CPE / SNR(&상/하향파워) / QOS 확인
show cable modem [mac-add] verbose
show cable modem [mac-add] verbose | include SNR
show cable modem [mac-add] verbose | include CPE
show cable modem [mac-add] verbose | include QoS

◎ (1.1) 상/하향 파워 및 SNR 확인
show cable modem [mac-add] phy

◎ (1.0/1.1) 각 포트 SNR 확인
show controllers c3/0 | inc SNR
show controllers [CMTS interface] | include SNR

◎ (1.0/1.1) upstream port 의 주파수 및 FEC 확인 (sch)
show cable hop

◎ (1.0) downstram port 의 주파수 확인
show controller cable3/0 | inc Fre / MHz

◎ (1.1/1.0) 상향 사용율(%) 확인
show interface c4/0 mac-s| include util (docsis 1.1)
show interface c4/0 up| include util (docsis 1.0)

◎ (1.0/1.1) 지정한 CM에 붙은 Host IP를 보고자 할때
show interface cable3/0 modem [sid-no]
show cable modem [mac-add] cpe

◎ (1.0/1.1) Ins / Hit / Miss / CRC 확인
show cable modem [mac-add] flap (docsis 1.1)
show cable flap | inc [mac-add] (docsis 1.0)
Ins - intermittent downstream sync loss or DHCP or modem registration porblems
(간헐적인 하향 싱크 손실 또는 DHCP나 모뎀 인증 문제)
Hit - The Number of times the CM responds to MAC layer keepalive message
(CMTS와 CM간의 keepalive message가 정상 도달하는 경우의 총수)
Miss - The Number of times the CM misses to MAC layer keepalive message
(CMTS와 CM간의 keepalive message가 손실되는 경우로
Hit와 Miss의 비율이 8% 미만이 정상이며 그 이상인 경우 상향측 문제로 추정가능)
CRC - The Number of cyclic redundancy check (CRC) errors from this CM
P-Adj - TX 파워가 3dB 이상 조정되는 경우 1 증가
Time - The most recent time that the CM dropped the connection

◎ (1.1) 각 포트별 소속 단국 확인-포트변경시 활용 (단, 파워콤만 가능)
show interface c4/0 up | include Des

◎ (1.0) 서로 다른 하향 사용시 포트변경 (단, 파워콤만 가능)
cable modem [mac-add] change-frequency [해당 하향주파수] [포트번호]
=> 현재 파워콤CMTS에서도 사용불가 (Dacom권한 없음-CICK포함)

◎ (1.0/1.1) 같은 하향 사용시 포트변경 #1 (Dacom권한 없음-CICK포함)
cable modem [mac-add] c [바꿀 포트번호]

◎ (1.0/1.1) 같은 하향 사용시 포트변경 #2
test cable ucc c3/0 [sid-no] [바꿀 포트순서]

◎ (1.0) 상향 포트별 사용중인 주파수를 동일 스펙트럼 그룹내 다른 주파수로 강제 변환
test cable hop c2/0 upstream [해당 포트번호]

◎ (1.0/1.1) offline 상태인 모뎀의 offline 된 시간 확인 (scm off | inc [mac-add])
show cable modem offline | include [mac-add끝자리]

◎ (1.0/1.1) 해당 셀에 붙은 Total/Active/Registered Modems 갯수 (scm su | inc 3/0)
show cable modem summary | include Cable3/0

◎ (1.1) 상/하향 사용량 감시 (scm c3/0 counters)
show cable modem c3/0 counters | inc [mac-add끝자리]
(MAC Address / US-Packets / US-Bytes / DS-Packets / DS-Bytes)

◎ (1.0) 상/하향 사용량 감시 (sh int c3/0 sid counters)
show interface c3/0 sid [sid-no] counters
* [sid-no] 생략시 전체 리스트 출력

◎ (1.0/1.1) 모뎀 리셋 (ccm [cm-ip] reset)
clear cable modem [mac-add or cm ip) reset

◎ (1.0/1.1) cm에 연결된 pc ip clear
clear cable host [pc ip]
cch [pc ip]/[pc mac-add]

▣ 데이콤 보라홈넷 기준치--------------------------------------
◎ CMTS측 상향 Power(CMTS에서 수신하는 파워) : 0±10 dBmV

◎ CM측 상향 Power(CM에서 송신하는 파워) : 43±10 dBmV
(55이상-과열 가능성 높음 / 적정값이하-품질저하)

◎ CM측 하향 Power(CM에서 수신하는 파워) : 0±10 dBmV (규격은 0±15)

◎ SNR : 상/하향 모두 30dB 이상 (Cisco 기준 : 29dB)
20dB미만인 경우 잦은 초기화현상을 발견할 수 있음

◎ Utilization : 70% 이하 (Cisco 기준 : 75% 이하)
상향사용율 90% 이상인 경우 병목현상으로 인한 속도저하 유발 (1M미만 ~ 30k)

▣ Cable Modem initial State------------------------------------
◎ init(r1) : CM이 initial ranging 을 보내고 있음
◎ init(r2) : CM은 ranging 상태
◎ init(rc) : CM ranging 완료
◎ init(d) : DHCP request를 받게 된다
◎ init(i) : DHCP reply received : IP address 할당
◎ init(t) : TOD exchange가 된다
◎ init(o) : option file transfer 가 시작된다
◎ online(d) : 모뎀은 정상 등록되었으나 CNR 에서 enable Network Access 체크누락
◎ online(pk) : 정상 사용 가능한 상태로 보안접속 상태임 (DHCP 별도 관리 가입자임)

syslog 를 이용한 원격로그지원
slog-8617.tgz

1. syslog 설명

전통적인 유닉스 시스템에서는, 시스템에서 발생하는 내용들에대해서 로깅(Logging)을

제공합니다.

물론 보안과 관리의 목적이며 이 로그 파일들은 운영체제마다 조금씩 틀리지만,
리눅스의 경우 /var/log 에 쌓이게 됩니다.

시스템 관리자는 일정 규칙에의해 설정을 하게 되며, 자신이 개발하는 프로그램에도 syslog
기능을 사용하는게 가능합니다.  syslog 기능은 syslogd 를  기동시킴으로서, 작동하게 되는데

물론 항상 떠 있어야 하겠고, 사용하는 관련 파일들로는 /etc/syslog.conf 가 주로 사용되고, 
/etc/sysconfig/syslog, 원격백업등을위해서 /etc/hosts 파일과,  /etc/services 파일등의 편집이
필요할 수도 있습니다.

2. syslog.conf 파일 설명

이 파일은 형식이, [selector]와 [action] 으로 나눠지며, 다시 [selector]는 [facility]와

[severity]로 나눠 집니다. 여기서 facility자리는 "어떤것에대해" 정도로  생각하면되고,

severity는 "우선순위" 입니다.  [action]은 보통 파일이름을 지정해서, 해당파일에 쓰란거죠.

여기다 원격지를 지정하면 원격지로  보냅니다.

정리하면, [facility][severity][action]은,  어떤것에대해(facility), 어떤 심각도(severity) 로,
어떻게 해라(action)  입니다.

[facility] 리스트 -----------------------------------------

kern: 커널
user: 사용자 레벨(일반 프로세스)
mail: 메일 서브 시스템
auth: 보안, 권한 프로그램들
daemon: 다른 시스템 데몬
news: 뉴스 서브시스템
local0-7:  다른용도 사용을위해 예약
* : 모든것

(이 외에도 몇가지가 더 있습니다.)

[severity] 리스트 ----------------------------------------

0 :  emergency 비상상태
1 :  alert 상태
2 :  critical 상태
3 :  error 상태
4 :  warning 상태
5 :  notice 상태
6 :  info 정보 메세지 (시스템 분석용)
7 :  debug (프로그램 디버그할때)
none : 이것이 facility와 사용되면 해당 facility는 제외,

[action] 필드 --------------------------------------------

파일명 : 해당 파일에 기록
@호스트명 : 해당 호스트로 전송

종합해서 샘플을 풀이해보자면,

mail.debug   /tmp/maillog
(mail 에대해, 상태는 debug로해서, /tmp/mailog 에 기록하라)

*.debug;mail.none    @myhost
(모든것에대해, 상태는 debug로, mail은 제외하고,  myhost로 전송하라)

conf설정에서 중요한것은 칸을 띄울때는 공백이 아니라, 탭으로 하여야 합니다.(중요!!!)

3. 원격 저장을 위한 설정

3.1  로그를 받는 쪽

로그백업을 원격지로 보내기위해서는, 보내려는 syslogd 를 기동시킬때,
/etc/sysconfig/syslog 파일을 열어서

SYSLOGD_OPTIONS="-m 0 -r"        
처럼 바꿔줍니다. -r 이 Remote 의미 입니다. 물론 위 설정을 안바꾸고 syslogd를 기동시킬때
옵션으로 줘도 되죠.

3.2  로그를 보내려는 쪽

/etc/hosts 파일을 편집합니다.  로그 서버를 giran이라고 칭하고, 도메인이 giran.uu.net 이며,
IP를  111.111.111.111 이라면

111.111.111.111   giran.uu.net  giran   loghost

처럼 설정을 해둡니다.  /etc/hosts 파일 형식은 참고로,
[IP-address fully-qualified-domain-name hostname "loghost"] 형식입니다.

이렇게만 해두면, 로그를 받는 서버측이 잘 작동하는것을 볼 수 있습니다.
하지만, 우리의 문제는 로그를 받는쪽 서버의 일개 계정 사용자 뿐이라는 거죠.
그래서 슈퍼유저가 아니라서, 받을수도 없고, 설정할 수도 없고, 기존 로그파일에
섞일 우려도 있고요.

3.3  일반사용자 계정으로 로그서버 설정 과 구축

A) /etc/services 파일 수정

이 기능을 사용하려면, 먼저 [보내는 쪽]에서 수정해야할게 /etc/services 파일을 열어서

syslog  514/udp

라고 되있는 부분을 1514 처럼 원하는 값으로 바꿔주세요.
(이 값은 후에나올, slog 툴에서 리슨 포트랑 일치해야 겠죠)

이렇게 하는 이유는 syslogd 는 원격지로 패킷을 보낼때, udp 514번을 이용합니다.
514번은 이미 글로벌하게 사용되는 포트이고, 우리는 사적으로 사용할 계획이니까요.

B) /etc/syslog.conf 파일 예제

*.info;mail.none;news.none     /var/log/messages
*.info;mail.none;news.none     @loghost

위에서, 첫줄은 보통 디폴트로 있는 구문입니다. 그 아래에 같은형식으로 적고, 파일이 아닌
호스트로 수정해주세요. 이렇게 같은걸 2줄 적는 이유는 동시에 처리되게 하려는거죠
로컬 로그파일에도 기록되고, 원격 호스트로도 보내고요.

C) /etc/hosts 파일 예제

111.111.111.111   giran.uu.net  giran   loghost

이것은 위에서 언급했습니다.

이렇게 해서 [로그를 보내려는 클라이언트]의 설정이 마무리 되었습니다.
서버측은 설정할게 없습니다. 단지 자신의 개인 계정에서 첨부 소스파일을 압축을 풀어
소스에서, LOG_HOME 수정후, 컴파일하여 실행시키면 됩니다.

#define LOG_HOME    "/user4/starzan/slog/"
처럼 되있는 부분을 자신의 계정의 디렉토리를 지정하면 되겠네요. 만약 포트가 충돌된다면,
소스에서 역시 포트 번호를 바꾸시면 되며, C 소스파일에 대해서는 설명을 생략합니다.
소스는 저도 손가는대로 짠이후 안봐서 버그가 있을수 있으니, 직접 고쳐 사용하시던지
아니면, 적어주세요. ^^

# tar xvfz slog.tgz

# make        (바이너리 만듦니다.)

# ./slog
# 죽일때는, kill  [pid]

이 slog는 로그파일을 원격지 ip별로 기록합니다. 저 같은경우 이렇게 실행 함으로서
여러대의 로그파일을 관리했죠.
즉,
111.111.111.111.log
111.111.111.112.log
111.111.111.113.log
처럼 패킷이 들어오는 ip에 따라 로그에 기록합니다. 그래서 서버별로 관리 하기 좋죠.

이상입니다.

(첨부소스는, 간단한 UDP 서버 입니다

[ 802.1 LAN/MAN architecture, Security, MAC & LLC layers ]

http://grouper.ieee.org/groups/802/1/

Active Project

Archived Projects

802 - Overview & Architecture

802a - Playpen Ethertypes

802b - Registration of Object Identifiers

802.1D (1998) - MAC bridges

802.1D (2004) - MAC Bridges

802.1G - Remote MAC bridging

802.1p - Traffic Class Expediting and Dynamic Multicast Filtering (published in 802.1D-1998)

802.1Q - Virtual LANs

802.1s - Multiple Spanning Trees

802.1t - 802.1D Maintenance

802.1u - 802.1Q Maintenance

802.1v - VLAN Classification by Protocol and Port

802.1w - Rapid Reconfiguration of Spanning Tree

802.1X - Port Based Network Access Control

802.1y - 802.1D Maintenance (published under 802.1D(2004))

802.1z - 802.1Q Maintenance - withdrawn

802.1AB - Station and Media Access Control Connectivity Discovery

[ 802.2 Logical Link Control (LLC) ]

http://grouper.ieee.org/groups/802/2/

Working Group (WG) 802.2 develops standards for Logical Link Control (LLC).

WG 802.2 is inactive (in "hibernation") with no new projects in development. Its completed work is a published standard, variously designated

ANSI/IEEE Standard 802.2, 1998 Edition, and

ISO/IEC 8802-2:1998.

On December 10, 2003, the IEEE-SA Standards Board approved the reaffirmation of Standard 802.2.

Participants in the reaffirmation ballot offered 39 comments, which the Working Group studied and discussed. Comments and committee rejoinders are preserved in a Comment Report, which may serve as a useful reference for understanding Std. 802.2.

CONTACT INFORMATION

The Chair of WG 802.2 is David Carlson.

The sponsor is the LAN and MAN Standards Committee (LMSC), a.k.a. Project 802.

ANSI/IEEE Standard 802.2, 1998 Edition is available online at the Get IEEE 802™ home page

[ 802.3 CSMA/CD (ETHERNET) ]

http://grouper.ieee.org/groups/802/3/

IEEE 802.3 Call for interest:

• A request for agenda time for a Short Haul 10Gb/s PHY call for interest has been received. It will be discussed during the IEEE 802 LMSC November 2005 Plenary meeting in Vancouver, BC, Canada.

The IEEE 802.3 Working Group develops standards for CSMA/CD (Ethernet) based LANs. We have a number of active projects as listed below:

• IEEE 802.3, Residential Ethernet Study Group.
  
• IEEE P802.3an, 10GBASE-T Task Force.
  
• IEEE P802.3ap, Backplane Ethernet Task Force.
  
• IEEE P802.3aq, 10GBASE-LRM Task Force.
  
• IEEE P802.3ar, Congestion Management Task Force.
  
• IEEE P802.3as, Frame Expansion Task Force.
  
• IEEE P802.3at, DTE Power Enhancements Task Force.
  
• IEEE P802.3-2005/Cor 1, Corrigendum 1 - Power over Ethernet Isolation.
  

Additional information:

Next IEEE 802.3 Interim meeting notice.

Next IEEE 802 Plenary meeting notice.

IEEE 802.3 related announcements.

IEEE 802.3 Plenary minutes.

IEEE 802.3 Maintenance.

IEEE 802.3 Interpretations.

IEEE 802.3 related Plenary tutorials.

IEEE 802.3 reflector policy.

IEEE 802.3 Management registration arcs.

IEEE 802.3 Auto-Negotiation selector fields.

IEEE 802.3 Private area (password-protected).

Other information:

Operating Rules of IEEE Project 802 Working Group 802.3, CSMA/CD LANs.

Requirements for Voting on IEEE 802.3 Drafts.

Typical Working Group 802.3 meetings during IEEE 802 Plenary Week.

Requesting an interpretation of the Standard.

IEEE 802.3 Patent policy.

Discussion of Cost in Working Group 802.3.

Published Standard:

IEEE 802 Standards Available for Free Download.

Purchasing published IEEE 802.3 Standards and drafts.

IEEE Standards On-Line Subscription Information.

IEEE Standards Ordering Information.

Publication Status of IEEE 802.3 Documents.

Correction sheets for published IEEE 802.3 Standard.

ISO/IEC approval status for published IEEE 802.3 Standard.

Machine readable extracts of published IEEE 802.3 Standard.

Archive Information of completed work:

IEEE 802.3 Trunking Study Group.

IEEE 802.3 Higher Speed Study Group.

IEEE 802.3 DTE Power via MDI Study Group.

IEEE 802.3 10GBASE-CX4 Study Group.

IEEE 802.3 10GBASE-T Study Group.

IEEE 802.3 Backplane Ethernet Study Group.

IEEE 802.3 10Gb/s on FDDI-grade MM fiber Study Group.

IEEE 802.3 Power over Ethernet Study Group.

IEEE Std 802.3z-1998, Gigabit Ethernet.

IEEE Std 802.3aa-1998, Maintenance #5.

IEEE Std 802.3ab-1999, 1000BASE-T.

IEEE Std 802.3ac-1998, VLAN TAG.

IEEE Std 802.3ad-2000, Link Aggregation.

IEEE Std 802.3ae-2002, 10Gb/s Ethernet.

IEEE Std 802.3af-2003, DTE Power via MDI.

IEEE Std 802.3ag-2002, Maintenance #6 (Revision).

IEEE Std 802.3ah-2004, Ethernet in the First Mile.

IEEE Std 802.3aj-2003, Maintenance #7.

IEEE Std 802.3ak-2004, 10GBASE-CX4.

IEEE Std 802.3REVam-2005, Maintenance #8 (Revision).

IEEE Std 1802.3-2001, Conformance Test Maintenance #1.

IEEE P802.3 Ethernet over LAPS liaison Ad hoc.

IEEE P802.3 Static Discharge in Copper Cables Ad hoc.

IEEE P802.3 100BASE-FX over dual Single Mode Fibre Call For Interest.

Contact Information:

• IEEE 802.3 Working Group Chair: Bob Grow.
  
• IEEE 802.3 Working Group Vice Chair: David Law.
  
• IEEE 802.3 Working Group Executive Secretary: Steve Carlson.
  
• IEEE 802.3 Working Group Secretary: Wael William Diab.
  
• IEEE Standards Staff Liaison: Andrew Ickowicz.
  
• List of Task Force chairs and editors.
  

[ 802.4 TOKEN BUS ]

http://grouper.ieee.org/groups/802/4/

The IEEE 802.4 Working Group develops standards for Token Bus. This working group is currently in hibernation (inactive) with no ongoing projects.

CONTACT INFORMATION

IEEE Standards Staff Liaison for IEEE 802: Denise Pribula.

IEEE 802.4 Hibernating Working Group Chair: Paul Eastman.

[ 802.5 Web Site ]

http://grouper.ieee.org/groups/802/5/

Working Group Standalone Documents

This is a set of standalone documents that support the committee's work. It includes:

• a committee mission statement
• committee membership list,
• committee voter and observer information
• a master list for meeting documents
• editorship rules and
• a list of outstanding maintenance work to be carried out by the committee.

Published Standards

8802-5 : 1998 (ISO/IEC) [ANSI/IEEE 802.5, 1998 Edition]

Information technology--Telecommunications and information exchange between systems--Local and metropolitan area networks--Specific requirements--
Part 5: Token ring access method and physical layer
• Standard details.
• Order from here.

802.5c-1991 (R1997) Supplement to IEEE Std 802.5-1989

Recommended Practice for Dual Ring Operation with Wrapback Reconfiguration (ANSI)

Standard details.

Order from here.

TR 11802-4 : 1994 (ISO/IEC) [ANSI/IEEE Std 802.5j-1993]

Supplement to ISO/IEC 8802-5 : 1992, Fibre optic station attachment (ISO/IEC Technical Report Type 2)

Standard details.

Order from here.

802.5:1998 / Amendment 1.:1998 Dedicated Token Ring Operation and Fibre Optic Media

This document contains IEEE Stds. 802.5r-1997 and 802.5j-1997 (both approved on September 16th, 1997. DTR is a mode of operation of token ring equipment on dedicated (i.e., point-to-point) links. It defines DTR Concentrators and DTR Stations. DTR Concentrators have C-Ports which have two modes of operation: Port mode, and Station emulation mode. Both DTR Concentrators and DTR Stations may support two access methods: token-passing (TKP) and transmit-immediate (TXI). The full power of DTR is seen on links operating with the TXI access protocol, because this protocol allows the link to carry data at full speed in both directions at once (full-duplex operation).

Standard details.

Order from here.

Archive Material

802.5 Physical layer tutorial material

Jim Carlo has collected the physical layer papers which have been presented to the 802.5 committee over the years. These papers represent a huge volume of expertise in the arcane field of token ring physical layer design.

Working Groups

P802.5t 100 Mbit/s Dedicated Token Ring

Project scope: Generate a standard for 100 Mbit/s 802.5 Token Ring LANs with MACs based on the present 802.5 Token Ring MAC. It will support 2-pair Category 5 (100 ohm) and STP (150 ohm) cabling based on the 802.3 100BASE-TX PHY and support transmission over optical fibre based on using the 100BASE-X PHY and the FDDI fibre PMD. The standard will consist of specifications for both stations and ports. The Media Access Control (MAX) will operate a dedicated Token Ring link, using the Transmit Immediate (TXI) Access Protocol as defined for 4/16 Mbit/s Token Ring operation with minimal modifications to support operation with the IEEE 802.3 100 Mbit/s Phyisical Layer (100BASE-X PHY). The Token Ring management objects defined for 4/16 Mbit/s operation will continue to be used for 100 Mbit/s operation. The frame format between MAC and LLC will be preserved.

• Project Approval Request
• IEEE Standards Status Report on P802.5t
• Working group documents.

P802.5v Gigabit Token Ring

Project scope: Define IEEE 802.5 Token Ring (MAC) parameters and minimal augmentation of its operation, physical layer characteristics, and management parameters for transfer of 802.5 format frames at 1,000 Mb/s or faster. The standard will consist of specifications for both stations and ports. MAC frame format will be based on that defined for IEEE 802.5. The frame format between MAC and LLC is being preserved

Project Approval Request

IEEE Standards Status Report on P802.5v

Working group documents.

P802.5w Errata to 802.5:1998 and Amd.1:1998

Project scope: Correct errors in 802.5 and its amendments.

Project Approval Request

IEEE Standards Status Report on P802.5w

Working group documents.

P802.5x Supplement to 802.1Q: Virtual Bridged LANs: Source Routing

Scope: Specify extensions to 802.1Q to enhance support for the source route bridging method.

Project Approval Request

IEEE Standards Status Report on P802.5x

Working group documents.

P802.5rev Token Ring standard revision

Scope: Unification of the token ring standards and supplements with clarification and corrections.

Project Approval Request

IEEE Standards Status Report on P802.5

Working group documents.

P802.5z Aggregation of Multiple Link Segments

Scope: Specify a DTE to DTE logical link which consists of n parallel instances of an 802.5 point-to-point link segment. The logical link will support existing 802.5 MAC clients.

Project Approval Request

IEEE Standards Status Report on P802.5z

Working group documents.

P802.5?? Enhanced Source Routing

Scope: The source route bridging method [802.1d] will be enhanced to provide additional resilience and may be enhanced to provide additional load sharing capabilities.

Project Approval Request

[ 802.6 METROPOLITAN NETWORKS ]

http://grouper.ieee.org/groups/802/6/

The IEEE 802.6 Working Group develops standards for Metropolitan Networks. This working group is currently in hibernation (inactive) with no ongoing projects.

CONTACT INFORMATION

IEEE Standards Staff Liaison for IEEE 802: Denise Pribula.

IEEE 802.6 Hibernating Working Group Chair: Jim Mollenauer.

[ 802.7 Broadband TAG ]

http://grouper.ieee.org/groups/802/7/

The IEEE 802.7 Broadband Technical Advisory Group (TAG) developed a recommended practice, IEEE Std 802.7 - 1989, IEEE Recommended Practices for Broadband Local Area Networks (Reaffirmed 1997). This group is inactive with no ongoing projects. The maintenance effort for IEEE Std 802.7 - 1989 is supported by 802.14.

CONTACT INFORMATION

IEEE Standards Staff Liaison for IEEE 802: Denise Pribula.

[ 802.8 FIBER OPTIC TAG ]

http://grouper.ieee.org/groups/802/8/

The IEEE 802.8 Technical Advisory Group (TAG) develops recommended practices for fiber optics.

CONTACT INFORMATION

IEEE Standards Staff Liaison for IEEE 802: Denise Pribula.

IEEE 802.8 Working Group Chair: Chip Benson.

[ 802.9 ISOCHRONOUS LANS ]

http://grouper.ieee.org/groups/802/9/

The IEEE 802.9 Working Group develops standards for Isochronous LANs.

CONTACT INFORMATION

IEEE Standards Staff Liaison for IEEE 802: Denise Pribula.

IEEE 802.9 Working Group Chair: Dhadesugoor Vaman.

[ 802.10 Standards for Interoperable LAN/MAN Security (SILS) ]

http://grouper.ieee.org/groups/802/10/

The SILS working group has completed its activities in developing LAN/MAN security standards. Although the group is inactive information may still be obtained through the contacts listed below.

STANDARDS

Get IEEE 802

MEMBERS ONLY INFORMATION

E-mail Reflector: std-802-10.

CONTACT INFORMATION

IEEE Standards Staff Liaison for IEEE 802: Andrew Ickowicz.

IEEE 802.10 Working Group Chair: Ken Alonge.

[ 802.11 WIRELESS LOCAL AREA NETWORKS ]

http://grouper.ieee.org/groups/802/11/

IEEE 802.11a-1999 (8802-11:1999/Amd 1:2000(E)), IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements—Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications—Amendment 1: High-speed Physical Layer in the 5 GHz band

IEEE 802.11b-1999 Supplement to 802.11-1999,Wireless LAN MAC and PHY specifications: Higher speed Physical Layer (PHY) extension in the 2.4 GHz band

802.11b-1999/Cor1-2001, IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements—Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications—Amendment 2: Higher-speed Physical Layer (PHY) extension in the 2.4 GHz band—Corrigendum1

IEEE 802.11d-2001, Amendment to IEEE 802.11-1999, (ISO/IEC 8802-11) Information technology--Telecommunications and information exchange between systems--Local and metropolitan area networks--Specific requirements--Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications: Specification for Operation in Additional Regulartory Domains

IEEE 802.11F-2003 IEEE Recommended Practice for Multi-Vendor Access Point Interoperability via an Inter-Access Point Protocol Across Distribution Systems Supporting IEEE 802.11 Operation

IEEE 802.11g-2003 IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements—Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications—Amendment 4: Further Higher-Speed Physical Layer Extension in the 2.4 GHz Band

IEEE 802.11h-2003 IEEE Standard for Information technology—Telecommunications and Information Exchange Between Systems—LAN/MAN Specific Requirements—Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications: Spectrum and Transmit Power Management Extensions in the 5GHz band in Europe

IEEE 802.11i-2004 Amendment to IEEE Std 802.11, 1999 Edition (Reaff 2003). IEEE Standard for Information technology--Telecommunications and information exchange between system--Local and metropolitan area networks?Specific requirements--Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications--Amendment 6: Medium Access Control (MAC) Security Enhancements

IEEE 802.11j-2004 IEEE Standard for Information technology—Telecommunications and information exchange between systems--Local and metropolitan area networks—Specific requirements—Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications—Amendment 7: 4.9 GHz–5 GHz Operation in Japan

[ 802.12 DEMAND PRIORITY ]

http://grouper.ieee.org/groups/802/11/

The IEEE 802.12 Working Group develops standards for Demand Priority.

CONTACT INFORMATION

IEEE Standards Staff Liaison for IEEE 802: Denise Pribula.

IEEE 802.12 Working Group Chair: Pat Thaler.

[ 802.15 Working Group for Wireless Personal Area Networks ]

http://grouper.ieee.org/groups/802/15/

ABOUT

The 802.15 WPAN?effort focuses on the development of consensus standards for Personal Area Networks or short distance wireless networks.  These WPANs address wireless networking of portable and mobile computing devices such as PCs, Personal Digital Assistants (PDAs), peripherals, cell phones, pagers, and consumer electronics; allowing these devices to communicate and interoperate with one another. The goal is to publish standards, recommended practices, or guides that have broad market applicability and deal effectively with the issues of coexistence and interoperability with other wired and wireless networking solutions.

The IEEE 802.15 Working Group is part of the 802 Local and Metropolitan Area Network Standards Committee of the IEEE Computer Society. The IEEE-SA is an international membership organization serving today's industries with a complete portfolio of standards programs. The IEEE has more than 368,225 members in approximately 150 countries. Through its members, the IEEE is a leading authority on areas ranging from aerospace, computers and telecommunications to biomedical engineering, electric power and consumer electronics.

For more information on 802.15 or to participate, contact Bob Heile (+1 781 222 1393 voice), bheile@ieee.org .

[ 802.16 Working Group on Broadband Wireless Access Standards ]

http://grouper.ieee.org/groups/802/16/

The IEEE 802.16 Working Group on Broadband Wireless Access Standards develops standards and recommended practices to support the development and deployment of broadband Wireless Metropolitan Area Networks. IEEE 802.16 is a unit of the IEEE 802 LAN/MAN Standards Committee, the premier transnational forum for wireless networking standardization.

People often take the view that standardization is the enemy of creativity. But I think that standards help make creativity possible -- by allowing for the establishment of an infrastructure, which then leads to enormous entrepreneurialism, creativity, and competitiveness.
-Vint Cerf, TCP/IP co-developer and Internet pioneer, in Fast Company, April 2000.

News

Session #39 held 12-15 Sept in Taipei; report to follow

Session #38 Report highlights results of meetings of 18-22 July 2004

IEEE 802.16 Project Development Milestone Schedules

Session Reports

General Information

Background Information on IEEE 802.16

Tutorials

Published IEEE 802.16 Standards and Drafts

Download some IEEE 802.16 Standards under Get IEEE 802^TM program

Liaisons and External Organizations

What People Are Saying about IEEE 802.16

Details (mainly for participants)

Upcoming Meetings (and previous ones)

Working Group Documents (also see TG & Liaison pages)

Unfiled Contributions

Task Groups and Committees

Working Group Letter Ballots

Key Development Resources

Participants, Participation, and Membership

Legal Issues

Submitting Documents

Search IEEE 802.16 Webspace

[ 802.17 Resilient Packet Ring Working Group ]

http://grouper.ieee.org/groups/802/17/

Working Group Description

The IEEE 802.17 Resilient Packet Ring Working Group (RPRWG) develops standards to support the development and deployment of Resilient Packet Ring networks in Local, Metropolitan, and Wide Area Networks for resilient and efficient transfer of data packets at rates scalable to many gigabits per second. These standards build upon existing Physical Layer specifications, and will develop new PHYs where appropriate. IEEE 802.17 is a unit of the IEEE 802 LAN/MAN Standards Committee.

In Metropolitan and Wide Area Networks, fiber optic rings are widely deployed. These rings are currently using protocols that are neither optimized nor scalable to the demands of packet networks, including speed of deployment, bandwidth allocation and throughput, resiliency to faults, and reduced equipment and operational costs.

Active Projects

802.17b Amendment

802.17 Maintenance

802.17 Interpretations

Completed Projects

802.17-2004 Base Standard

802.17a-2004 Amendment

Working Group Contact Information

Chair:	Mike Takefman
Vice Chair:	John Lemon
Secretary:	Volunteer Needed
Webmaster:	John Lemon
IEEE Standards Staff Liaison for IEEE 802:	Sue Vogel

[ 802.18 LAN/MAN Standards Committee 802.18 - the Radio Regulatory TAG ]

http://grouper.ieee.org/groups/802/18/

Introduction

IEEE 802, the LAN/MAN Standards Committee, or LMSC, currently has 6 Working Groups with projects on standards for radio-based systems ... IEEE 802.11 (WLAN), IEEE 802.15 (WPAN), IEEE 802.16 (WMAN), IEEE802.20 (Wireless Mobility), IEEE 802.21 (Handoff/Interoperability Between Networks), and IEEE 802.22 (WRAN).

Therefore, monitoring of, and active participation in, ongoing radio regulatory activities, at both the national and international levels, are an important part of LMSC's work. That is the job of the 802.18 Radio Regulatory Technical Advisory Group ("RR-TAG"). Any suggestions for improvements to these pages to make them more useful will always be welcome and may be sent to Michael Lynch.

Hot Items

The 802.18 RR-TAG September interim meeting will be held in Geneva, Switzerland, from 19 - 23 September.  The RR-TAG will be meeting in the ITU facility.  The meeting will provide RR-TAG attendees exposure to the ITU-R process, allow ITU-R meeting attendees to learn what the function of the RR-TAG is and to encourage participation in the IEEE process.

The meeting announcement will be sent 21 August to the RR-TAG reflector.  For further details, to include registration, please contact the RR-TAG chair.

The link is up now and available for the September joint wireless interim session (excluding the RR-TAG) in Orange County.

A link is also available for the January joint wireless interim session in Hawaii.  It is advisable to book your hotel well in advance.

[ 802.19 Coexistence Technical Advisory Group (TAG) ]

http://grouper.ieee.org/groups/802/19/

IEEE 802.19 TAG GENERAL INFORMATION

802.19 Meeting Plan Information.

802.19 Closing Reports.

802 Policies & Procedures

• Coexistence Assurance Excerpt:
  • "6.4 Technical Feasibility
    d) Coexistence of 802 wireless standards specifying devices for unlicensed operation.  The working group proposing a wireless project is required to demonstrate Coexistence through the preparation of a Coexistence Assurance (CA) document unless it is not applicable.
    • Working Group will create a CA document as part of the balloting process.
    • Working Group will not create a CA document
      • Reason it is not applicable: ___________________________________"
  • "22. Procedure for Coexistence Assurance (Formally Procedure 11)
    If indicated in the five criteria, the wireless working group shall produce a coexistence assurance (CA) document in the process of preparing for working group letter ballot and sponsor ballot.  The CA document shall accompany the draft on all wireless working group letter ballots.  The CA document shall address coexistence with all relevant approved 802 wireless standards specifying devices for unlicensed operation. The working group should consider other specifications in their identified target band(s) in the CA document.  The 802.19 TAG shall have one vote in working group letter ballots that include CA documents.  As part of their ballot comments, the 802.19 TAG will verify the CA methodology was applied appropriately and reported correctly.  The ballot group makes the determination on whether the coexistence necessary for the standard or amendment has been met if the ballot passes.  A representative of the 802.19 TAG should vote in all wireless sponsor ballots that are in the scope of the 802.19 coexistence TAG." Source: Revised effective March 21, 2005, LMSC_P&P_MARCH_2005_R050722.DOC

802.19 Policy and Procedures Adobe Acrobat (228KB).

802.19 list of projects requiring a CA document.

802.19 Submission Templates:

MS Word (37KB). 

MS PowerPoint (57KB).

Search 802.19 Web Site.

E-Mail Reflector.

IEEE 802.19 TAG ARCHIVED INFORMATION

802.19 Mailing-List archive by date by thread.

Document Archives.

IEEE 802.19 TAG CONTACT INFORMATION

IEEE 802.19 TAG Chair: Steve Shellhammer

IEEE 802.19 TAG Vice Chair: Tom Siep

IEEE 802.19 TAG Editor: David Cypher

IEEE 802.19 TAG Secretary: Steve Whitesell

IEEE 802.19 TAG Sponsor: Paul Nikolich

IEEE Standards Staff Liaison: Andrew Ickowicz

IEEE 802.11 Liaison: Sheung Li

IEEE 802.15 Liaison: Tom Siep

---

RELATED LINKS

IEEE Wireless Zone

IEEE 802.11 WLAN

IEEE 802.15 WPAN

IEEE 802.16 WMAN

IEEE 802.18 RR TAG

IEEE 802.20 MBWA

IEEE 802.21 Media Independent Handoff Working Group

IEEE 802.22 WRANs

IEEE 802 LAN/MAN Standards Committee

IEEE Computer Society

IEEE Site Map

[ 802.20 Mobile Broadband Wireless Access (MBWA) ]

http://grouper.ieee.org/groups/802/20/

IEEE 802.20 Mission and Project Scope

On 11 December 2002, the IEEE Standards Board approved the establishment of IEEE 802.20, the Mobile Broadband Wireless Access (MBWA) Working Group.

• Mission

  The mission of IEEE 802.20 is to develop the specification for an efficient packet based air interface that is optimized for the transport of IP based services. The goal is to enable worldwide deployment of affordable, ubiquitous, always-on and interoperable multi-vendor mobile broadband wireless access networks that meet the needs of business and residential end user markets.
  

• MBWA Scope

  Specification of physical and medium access control layers of an air interface for interoperable mobile broadband wireless access systems, operating in licensed bands below 3.5 GHz, optimized for IP-data transport, with peak data rates per user in excess of 1 Mbps. It supports various vehicular mobility classes up to 250 Km/h in a MAN environment and targets spectral efficiencies, sustained user data rates and numbers of active users that are all significantly higher than achieved by existing mobile systems.

[ 802.21 ]

http://grouper.ieee.org/groups/802/21/

Welcome

IEEE 802.21 is developing standards to enable handover and interoperability between heterogeneous network types including both 802 and non 802 networks.

Membership

The rules governing attaining voting member status are here:

Membership

Submissions

If you would like to post a file on these pages, please send the file to the address below and the file will be posted in the appropriate area within the web site.

First Read: Submitting Documents

Then send file to: Ajay Rajkumar

Working Group Documents

Current work items are based on the PAR:

PAR

Five Criteria doc

Latest draft

Documents and submissions toward the current work items are copyright of the IEEE but publicly available here. There is a separate server for the conferences, so there can be some lag time for updates between the two servers.

November 2005

September 2005

July 2005

May 2005

March 2005

January 2005

November 2004

September 2004

July 2004

May 2004

March 2004

[ 802.22 LAN/MAN Standards Committee 802.22 WG on WRANs (Wireless Regional Area Networks) ]

http://grouper.ieee.org/groups/802/22/

Introduction

IEEE 802.22, the Working Group on Wireless Regional Area Networks ("WRANs") is the newest Working Group in the IEEE 802 LMSC.

Its charter, under the PAR approved by the IEEE-SA Standards Board is to develop a standard for a cognitive radio-based PHY/MAC/air_interface for use by license-exempt devices on a non-interfering basis in spectrum that is allocated to the TV Broadcast Service.

Meeting documents will be posted, on a per meeting basis, on this website, as soon as possible after the conclusion of meetings, and will be available via an index under the "Meeting Documents" link in the link bar at the left of this page.

A "Members Only" directory, with password protection, has been established under the "Members Only Documents" tab in the link bar, but currently has no content other than a "placeholder" page. When "members only" content is generated, an e-mail will be sent to those entitled to access the private area with the required userid and password to gain access..

Any suggestions for improvements to these pages to make them more useful, or reports of broken links, will always be welcome and may be sent to Carl Stevenson.

HOT ITEMS

---

The IEEE 802 November 2005 Plenary Session Event Portal is NOW available for meeting registration and hotel reservations at: http://ieee802.facetoface-events.com/plenary/

This portal now includes the Visa Invitation Letter as well, however all potential attendees must registered for this Session prior to receiving the letter.

---

Please find the January 2006 IEEE 802 Wireless Interim Session meeting announcement at: http://ieee802.facetoface-events.com/wireless/. Since this Session will be held in Waikoloa, Hawaii, some important preliminary meeting information (especially Early Bird room rates) is included in this document.  REGISTRATION SERVICES WILL BE AVAILABLE SOON FOR THIS JANUARY 2006 SESSION!!

---

Call for Notice of Intent to Propose - Deadline Extended (again)

Due to a number of requests for an extension, the deadline has been extended again. Those intending to submit proposals for consideration towards a baseline upon which the first draft of the IEEE 802.22 Standard will be based must notify the Chair of the WG by e-mail no later than 6:00 pm, EDT, on Saturday, October 15th, 2005. There will be NO further extensions of this deadline.

Requirements Document and Channel Model Approved

The Requirements and Channel Model documents wer approved at our September interim meeting in Garden Grove, CA, and are now available in the September 2005 area of "Meeting Documents"
(document numbers 22-05-0007-46-0000 and 22-05-0055-07-00 respectively)
The Channel Model document is in the process of being editorially incorporated into the Requirements document as Appendix C and revision 47 of the Requirements document will be posted as soon as that editorial task has been completed (merging two Word docs with different formatting and styles without making a mess of things is a tedious task).
Until the merged document is posted in the September 2005 directory, the separate documents should meet the needs of those who are preparing proposals.

Call for Proposals

A "Call for Proposals" has been issued via the IEEE 802.22 e-mail reflector and cc'd to the Chairs of the other Wireless WGs and TAGs for forwarding to their e-mail reflectors. A copy of the Call for Proposals document is available in the November 2005 section of "Meeting Documents." Remember the deadline for submitting a "Notice of Intent to Propose." Proposals will only be accepted from proposers who meet the notice requirement.

last update. 2005-10-24.